[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Proposal for improving our issue list
|
All, Below is a proposal for how I think we could improve our
issue list. This is very consistent with how I will run the issue list for
WS-SX which is of course based on my experience from our existing issue list
and some suggestions that have been made during that time. Differences to our
current process our called out below. The biggest difference is the statuses have been
streamlined.
I have also noted differences from our current process
below. Regards, Marc g -------------------------- Issues life cycle Raising an issue: - Issue is raised in email, with a description, indication
of which document and draft the issue targets, and a proposed resolution if
possible (one issue per email) - Issue is assigned a number (in sequence), logged, and
assigned a status of “new” (see below) by the issues list coordinators - TC member raising the issue is assigned as initial owner - Issue is discussed via the TC list and in conference calls
/ f2f meetings as determined by the co-chairs, based on priorities set by the
TC - Ownership of the issue may be transferred to another TC
member if appropriate. Originator will be maintained in history. Issue status: · New Opened, but not yet accepted by the
TC. The co-chairs will schedule it on a meeting agenda as appropriate to
determine whether it is accepted or dropped. We’ve agreed to set a
low bar for issues, so this status is not intended to imply that a lengthy
discussion of each issue is required to determine if it is accepted or
not. This status implies that the TC has not reviewed to verify that the
issue is not a duplicate, etc. Previously this
would have been the issues in the proposed new issue list mail. Keeping them in
the issue list gives better tracking of what has been raised, particularly for
issues we decide to drop. · Active
Accepted by the TC as an
issue. In discussion. This is just Open,
no real difference. · Deferred
Accepted by the TC as an
issue. Discussion deferred (based on priorities, how this issue relates
to others, etc.). We already use
this one. · Pending
TC has agreed on a resolution.
Conference call or F2F minutes should reflect the agreement and decision.
In the editors’ queue to be applied to the target document. This is the same
in our current process. · Review Editors have applied the agreed
resolution to the document. The draft the issue is applied in will be
tracked. This is
effectively the Done status in our current process. · Closed TC has voted to approve the change
by voting to accept the draft to which the change was applied, determined it is
a duplicate, or no action is required. The reason it was closed will also be
tracked. The main
difference here from our current process is that we move directly to Closed
with no intermediate step of holding issues as Resolved until they are present
in a CD. ------------------------------------ Submitting an issue ------------------------------------ Send an email proposing the issue using the following
template: ------------------------------------ Subject: NEW Issue: [descriptive title] To: ws-rx@lists.oasis-open.org;
PLEASE DO NOT REPLY TO THIS EMAIL OR START
A DISCUSSISON THREAD UNTIL THE ISSUE IS ASSIGNED A NUMBER. The issues coordinators will notify the
list when that has occurred. Protocol: wsrm / wsrmp / rddl [Please include name and link to the document referenced,
i.e. wsrm-cd-02 http://docs.oasis-open.org/ws-rx/wsrm/200512/wsrm-cd-02.pdf ] Artifact: spec / soap / wsdl / schema / policy / all Type: [admin / design / editorial] Admin is a new type, this effectively
allows us to track AIs in the issue list. This gives us a single place to look,
better tracking of how we resolved our AIs, and as a side benefit also means we
don’t have to use Kavi for AI tracking. Title: [concise summary of the issue] Description: [detailed description, please include section and line
numbers where possible] Related issues: [numbers of related issues, if any] Proposed Resolution: [proposed resolution and text if appropriate (including
section and line numbers indicating where the text would be inserted or what it
would replace)] ------------------------------------ I will pick the issue up and give it a number (in sequence),
assigning the individual who submitted the email as owner of the issue. I will
send an email to the list with the issue number once it is assigned.
Subsequent mail threads should use the Issue xxx: format in the subject
line, where ‘xxx’ is the issue number. Please include only one issue per email and do not engage in
discussing the issue until it is assigned a number so we don’t have
multiple impossible to distinguish ‘NEW Issue’ threads on the list. ------------------------------------------ Issues tracking mechanism ------------------------------------------ We will continue to use the XML/XSL: http://docs.oasis-open.org/ws-rx/issues/ReliableMessagingIssues.xml At the issue level, the following will be tracked: · Number · Status · Protocol · Artifact (will
now allow multiple choices) · Type · Title · Description · Related
Issues · Origin (originator
and link to originating email) · Owner · Proposal
“x” (one for each proposal) · Resolution
(e.g., Proposal “x” accepted on [link to conf call / f2f meeting
notes detailing the acceptance] I will continue to update the issue list so that it is
current prior to every TC call or F2F. Technical Diplomat Microsoft Corporation Tel: (425) 703-1903 Blog: http://spaces.msn.com/members/mrgoodner/
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]