20 likes | 133 Vues
This document outlines the WS-RX Technical Committee (TC) process for resolving issues during specification development. TC members can raise issues during email discussions or meetings, and only those agreed upon are officially logged. The status of issues varies from Open-Unassigned to Closed, with designated steps for resolution, including TC discussions, volunteer assignments, and editor updates. The process emphasizes clear communication and documentation to ensure resolutions are minuted and followed through, ultimately leading to formal voting and closure of issues.
E N D
WS-RX TC Process for Specification Development TC discussion to understand the issue, its scope, etc TC agrees upon resolution A TC Member Raises an issue. TC Review TC Vote for CD TC decides to log the issue WD y WD z CD a WD x Spec Status Queue for Editors Issue Status Open- Unassigned Open- Assigned Editor- Pending Editor- Done TC- Reviewed Closed WD: Editors Draft CD: Committee Draft
Issues Life Cycle • TC members raise issues via email or during conf-calls/F2F meetings. Only issues that are agreed upon and minuted in the conf-calls and F2F meetings are logged. Issue Status: Open-Unassigned No member actively working on resolution Open-Assigned TC member(s) volunteered to propose resolution • Open issues are discussed via email, during conf-calls and F2F meetings. Resolutions are agreed upon and minuted during conf-calls and F2F meetings Issue Status: Editor-Pending • Editors update the specs to incorporate the resolution of Editor-Pending issues Issue Status: Editor-Done • Light weight process for reviewing Editor-Done issues (e.g. one or more TC members volunteer and review the changes to the spec) Issue Status: TC-Reviewed • Formal TC vote for CD brings to closure the new issues addressed by the voted revision Issue Status: Closed