- From: John Arwe <johnarwe@us.ibm.com>
- Date: Fri, 24 Aug 2007 13:15:15 -0400
- To: public-sml@w3.org
- Message-ID: <OFB6107604.9616C791-ON85257341.005EAE88-85257341.005EE824@us.ibm.com>
what is the semantic difference between keyword=resolved and status=resolved for our bugs? Best Regards, John Street address: 2455 South Road, Poughkeepsie, NY USA 12601 Voice: 1+845-435-9470 Fax: 1+845-432-9787 ----- Forwarded by John Arwe/Poughkeepsie/IBM on 08/24/2007 01:14 PM ----- "Smith, Virginia (HP Software)" <virginia.smith@hp.com> Sent by: member-sml-request@w3.org 08/02/2007 04:52 PM To <member-sml@w3c.org> cc Subject [w3c sml] Action 108 - tracking bugs Please review the attached diagram. This is a proposal from the editors to track the state of bugs. The ovals are actions performed by the WG and the rectangles represent keywords we can use to track the bug status. This proposal is a (very) simplified version of what the schema group is doing. Keywords (they are lower case / camel case): No keyword - the bug is new and ready for triage. 'needsAgreement' - the bug is being discussed or otherwise waiting on some action and not yet ready for the editors. 'editorial' - the bug is ready for an editor to take it and perform the required editorial action based on the resolution agreed upon by the WG. Note that anyone entering a simple 'typo' bug should add this keyword when they submit the bug so we don't spend time on triage for typos. 'needsReview' - the editorial change is complete but the editor would like the WG to review the change. This state may be skipped. That is, the editor may choose to move the bug directly to 'resolved' if she feels that no review is necessary. 'resolved' - the bug is resolved. I will change the bugs we reviewed today to add the appropriate keywords - assuming I don't get any major objections to this proposal. -- ginny [attachment "BugzillaProcess.pdf" deleted by John Arwe/Poughkeepsie/IBM]
Received on Friday, 24 August 2007 17:15:37 UTC