Changes between Version 1 and Version 2 of WorkingConventions/BugTracker


Ignore:
Timestamp:
Oct 28, 2010 1:21:48 PM (4 years ago)
Author:
igloo
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • WorkingConventions/BugTracker

    v1 v2  
    4747 * '''Owned by''' says who is committed to taking the ticket forward.  We typically leave this field blank until we actively start working on it, lest others feel unable to to work on a ticket because it is apparently owned, even though nothing is happening. 
    4848 
    49 == Releases == 
    50 When a release is made, any open tickets on that release's milestone will be moved to the next release's milestone. However, if they are more than 1 major release old (e.g. opened on the 6.10 branch, and about to be moved to the 6.14.1 milestone), and there is not a reason to keep them in the release milestone (e.g. a patch attached for review, or significant support in the CC field), then they will be moved to the `_|_` milestone instead. 
     49== Remilestoning tickets after a releases == 
     50 
     51When a release is made, any open tickets on that release's milestone will be moved to the next release's milestone. 
     52 
     53However, when moving onto a milestone for a later major release, the priority is dropped one level (or moved to `_|_` if it is already lowest) - unless one of these is true: 
     54 * priority > normal 
     55 * contains a patch for review 
     56 * significant support in the CC field 
     57 
     58For example, let us follow a ticket about a bug in 7.0.x that doesn't get fixed. 
     59 * Created in a 7.2.x milestone, priority normal 
     60 * When 7.2 branch is closed, moved to a 7.4.x milestone, priority low 
     61 * When 7.4 branch is closed, moved to a 7.6.x milestone, priority lowest 
     62 * When 7.6 branch is closed, moved to a `_|_` milestone, priority normal 
     63If it were initially filed in a 7.0.x milestone then it would remain priority normal when moved to 7.2.x. 
    5164 
    5265== Workflow ==