Changes between Version 47 and Version 48 of WorkingConventions


Ignore:
Timestamp:
Apr 28, 2010 1:26:43 PM (4 years ago)
Author:
igloo
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • WorkingConventions

    v47 v48  
    3636The following are GHC-specific policies regarding the fields of the Trac bug tracking system. (See also [wiki:ReportABug the bug reporting guidelines].) 
    3737 
    38  * '''Milestone''': this field is for the GHC development team to indicate by when we intend to fix the bug.  We have a milestone for each branch (e.g. "6.12-branch"), and three special milestones: 
     38 * '''Milestone''': this field is for the GHC development team to indicate by when we intend to fix the bug.  We have a milestone for each planned release (e.g. "6.12.3"), and three special milestones: 
    3939   * An empty milestone field means the bug has not been triaged yet.  We don't yet know if the 
    4040     ticket is a real, unique, issue.  Once this has been established, the ticket will be given 
     
    4848   severity might be reduced if we discover a workaround. 
    4949 
    50  * '''Priority''': this field is for the GHC development team to help us prioritise what we work on. On a branch milestone, the highest priority tickets are blockers for the next release on that branch, and the high priority tickets are those that we also plan to fix before releasing. We will also try to fix as many of the normal and lower priority tickets as possible. 
     50 * '''Priority''': this field is for the GHC development team to help us prioritise what we work on. On a release milestone, the highest priority tickets are blockers for that release, and the high priority tickets are those that we also plan to fix before releasing. We will also try to fix as many of the normal and lower priority tickets as possible. 
    5151 
    5252 * '''Test Case''': fill in this field with the name of the test in the test suite.  Typically every bug 
    5353   closed should have an appropriate test case added to the test suite. 
    5454 
    55 When stopping work on one branch (e.g. the 6.12 branch), all tickets on that branch's milestone will be moved to the next branch's milestone (e.g. 6.14-branch) unless they are more than 1 release old (e.g. opened on the 6.10 branch), in which case they will be moved to the `_|_` milestone instead. However, tickets with a patch attached for review, or with significant support (in the CC field) will not normally be moved to `_|_`. 
     55When 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. 
    5656 
    5757The ticket workflow is illustrated in the following image. Most tickets will start in state "new" and, once fixed, possibly go via state "merge" if they are suitable for merging to the stable branch, before moving to state "closed". They may also go via state "infoneeded" if more information is needed from the submitter, or "patch" if a patch that needs review has been attached to the ticket.