1. Proposed TC Issues Process
Martin Chapman

2. Purpose An issues driven process helps to
Untangle un-conflate problems
Narrow focus to solving particular bugs, improvements, new features etc
Set agendas and run meetings
Measure progress – e.g. ship when no more issues
Dovetails with Public Reviews

3. Lifecycle New Issue Closed Open Resolved Applied Deferred Accepted
Change Agreed
Rejected
Duplicate/No longer relevant
Address in future version
Resolved
Reopen
Reopen
WD Updated
Edits Rejected
Applied
Deferred
Edits Approved

4. New Issue Raised by TC Members at and in between meetings Include:
Short title
Detailed description of the
including version and page numbers where possible
MAY propose a solution
Recorded in TC’s JIRA
Issue number allocated at this stage even though may not be accepted as an issue

5. Open State No issue in a TC may be worked upon unless it is opened
Only discussion on new issue is to clarify and decide whether to open or not
An opened issue is
a new issue that has been voted to be opened
Does not imply acceptance of any proposed resolution
a closed/deferred issue that has been voted to be reopened (super majority vote here)
Discussion of an issue can take place in meetings, on JIRA, and the mailing list
If in MUST contain a subject line that includes “ISSUE: [issue number]”

6. Resolved State
A solution to an issue has been agreed by vote of the TC
The solution requires changes to a document
A resolved state means changes are agreed, but have not yet been incorporated into an agreed working draft
Precise wording changes as far as possible
Some resolutions may delegate to editors

7. Applied State
Editors have incorporated agreed resolution into a working draft.
Editors only change a working draft by applying resolved issues.
A rejected edit places the issue back into resolved state.
Edits are approved by a TC adopting a new Committee Draft that contains the edits.

8. Closed State An issue that will not be worked on anymore by the TC
A new issue deemed out of scope, inappropriate, malformed etc
A duplicate of another issue
An open issue that is now no longer relevant.
A resolved issue whose applied changes have been incorporated into a committee draft
Sub-state to record whether rejected, duplicate, fixed, no action

9. Deferred State
An issue that is valid but agreed to be addressed in a future version of the spec.
It is not closed.

10. Re-opening an Issue A Closed or Deferred Issue can be re-opened.
Requires a Special Majority vote via web ballot run by the TC chair(s)
Hence a very strong justification needed
Standing rule required
Re-opening does not undo a previously resolved issue (i.e. “un-edits”), but new resolution must take old resolution into account.

11. Raising the Bar
With the exception of re-opening an issue all transitions require a majority vote
As we get closer to finishing it is typical to raise the bar to open new issues.
Future standing rule and time to be decided by the TC

12. JIRA TC JIRA (OASIS hosted) to record all issues
Allocate issue numbers
Record state changes
Record resolutions and major decisions on an issue.
Always include public links to Minutes where decisions made.
Comments/discussion can take place on JIRA and on .
Editors can work off the “resolved” issues queue