← Prev in month ← Prev in thread
Next in thread → Next in month →

Issues Process

From
Ram Jeyaraman <>
Date
2008-09-16T17:47:43+00:00
ID
Thread
Issues Process
Issues Process

Issue Submittal

An issue,
submitted via email to the Technical Committee (TC) mailing list, must contain
the following details:

 
A
     statement at the top to discourage discussion of the issue until it is
     assigned a number. For example: "Please defer discussions on this
     issue until a time this issue is accepted and is assigned a number". 

 
A
     link to the target documents. 

 
The
     PDF line numbers. 

The submitted
issue may contain a proposed resolution.

Exactly one
issue is allowed per email. The email must have a subject line "NEW Issue:
xxx".

Issue Lifecycle

 
Issue
     is submitted. 

 
Issue
     is assigned a sequential number, logged, and assigned a status
     "Review", by the issues list editors. The TC member submitting
     the issue is assigned as the initial owner of the issue. 

 
Issue
     is discussed via the TC mailing list, conference calls, and face-to-face
     meetings, as determined by the TC chair, based on the priorities set by
     the TC. Ownership of the issue may be transferred to another TC member, if
     appropriate; however, the issue originator will be maintained in history.
     During its lifetime, an issue may go through different stages, as
     reflected by its status. 

Issue status

 
Review

     

     Opened, but not yet accepted by the TC. The TC chair will schedule the
     issue for discussion during a TC meeting, to determine whether to accept
     or drop the issue.

       

 
Dropped

     

     The TC has dropped the issue. This may be because the issue is a
     duplicate, not an issue, no action is required, or the originator has
     withdrawn the issue. The reason why the issue was dropped is documented in
     issue history.

       

 
Active

     

     Accepted by the TC as an issue. The issue is open for discussion.

       

 
Deferred

     

     Accepted by the TC as an issue. But further discussion on the issue has
     been deferred. This may happen due to issue priorities, or the
     relationship of the issue to other related issues.

       

 
Pending

     

     TC has agreed on a resolution. The resolution is in the specification
     editor's queue to be applied to the target documents. TC conference call
     or face-to-face meeting minutes must reflect the agreement and the
     decision.

       

 
Done

     

     Specification editors have applied the resolution to the specification
     draft. The applied changes need to be reviewed and accepted by the TC.

       

 
Resolved

     

     The specification changes have been reviewed and accepted by the TC.

       

 
Closed

     

     The TC has voted to approve the change by voting to accept the
     specification draft to which the change was applied.
← Prev in month ← Prev in thread
Next in thread → Next in month →