Changes between Version 6 and Version 7 of TicketLifeCycle

Timestamp:

Sep 2, 2010, 8:47:52 AM (14 years ago)

Author:

Krzysztof Studnik

Comment:

--

TicketLifeCycle

@@ -30 +30 @@
 == Analyzing ==
 
-Once confirmed, the research starts to identify the source of the problem. A core developer could "Accept" the ticket. Ticket gains status {{{assigned}}} automatically, indicating that work is already in progress for it, avoiding duplicated work. 
+Once confirmed, the research starts to identify the source of the problem. A core developer could '''Accept''' the ticket. Ticket gains status {{{assigned}}} automatically, indicating that work is already in progress for it, avoiding duplicated work. 
 
 The assignee, the reporter or other could come with some more information at this point, to help on the analysis research and coding.
@@ -36 +36 @@
 == Proposing Patches ==
 
-A proposed patch should be added as a new attachment to the ticket. It must be a valid SVN patch file, named XYZ.patch, where "XYZ" stands for the ticket number. 
-The  keyword should be appended to the ticket, indicating that the patch awaits review.
+A proposed patch should be added as a new attachment to the ticket. It must be a valid SVN patch file, named ''XYZ.patch'', where "XYZ" stands for the ticket number. 
+The  keyword '''HasPatch''' should be appended to the ticket, and selected action should be set as ''put on review'', indicating that the patch awaits review.
 
-If the submitter of a patch changes their mind about wanting a review, the review keyword should be removed.
-
-The "HasPatch" keyword, if available, should be removed at this point.
-
-When a submitter proposes an updated patch, the previous patch should still remain in the ticket. The new patch should be named "XYZ_n.patch", where "n" is a progressive number starting from "2". The new patch makes previous ones obsolete. The review flag should be set to "Review?" again, with instructions to the reviewer.
+When a submitter proposes an updated patch, the previous patch should still remain in the ticket. The new patch should be named ''XYZ_n.patch'', where "n" is a progressive number starting from "2". The new patch makes previous ones obsolete. The review status should be set again, with instructions to the reviewer.
 
 == Reviewing Patches ==