Changes between Version 6 and Version 7 of TicketLifeCycle


Ignore:
Timestamp:
Sep 2, 2010, 8:47:52 AM (9 years ago)
Author:
Krzysztof Studnik
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TicketLifeCycle

    v6 v7  
    3030== Analyzing ==
    3131
    32 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.
     32Once 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.
    3333
    3434The assignee, the reporter or other could come with some more information at this point, to help on the analysis research and coding.
     
    3636== Proposing Patches ==
    3737
    38 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.
    39 The  keyword should be appended to the ticket, indicating that the patch awaits review.
     38A 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.
     39The  keyword '''HasPatch''' should be appended to the ticket, and selected action should be set as ''put on review'', indicating that the patch awaits review.
    4040
    41 If the submitter of a patch changes their mind about wanting a review, the review keyword should be removed.
    42 
    43 The "HasPatch" keyword, if available, should be removed at this point.
    44 
    45 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.
     41When 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.
    4642
    4743== Reviewing Patches ==
© 2003 – 2019 CKSource – Frederico Knabben. All rights reserved. | Terms of use | Privacy policy