Changes between Version 43 and Version 44 of WorkingConventions


Ignore:
Timestamp:
Apr 28, 2010 12:52:27 PM (5 years ago)
Author:
igloo
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • WorkingConventions

    v43 v44  
    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  * '''Type''': When a bug is fixed, but the patch or patches still need to be merged to other branches, then
    39    don't close the bug, just change its type from '''bug''' or '''task''' to '''merge'''.  Also add a list of
    40    patches to be merged, and which branch to merge to, as a comment.
     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:
     39   * An empty milestone field means the bug has not been triaged yet.  We don't yet know if the
     40     ticket is a real, unique, issue.  Once this has been established, the ticket will be given
     41     a milestone.
     42   * '''Not GHC''' is for tickets that are not tied to a GHC release.
     43   * '''_|_''' is for tickets that have been triaged, but we don't plan to fix them for a particular
     44     release.  This might be because the bug is low priority, or is simply too hard to fix right now.
    4145
    4246 * '''Severity''': this is set by the submitter of the ticket, and indicates how important the issue is to
     
    4448   severity might be reduced if we discover a workaround.
    4549
    46  * '''Priority''': this field is for the GHC development team to help us prioritise what we work on.  Bugs
    47    that have a high severity will tend to be prioritised higher, as will bugs that are regressions from
    48    a previous release.
    49 
    50  * '''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 release, and three special milestones:
    51    * An empty milestone field means the bug has not been triaged yet.  We don't yet know if the
    52      ticket is a real, unique, issue.  Once this has been established, the ticket will be given
    53      a milestone.
    54    * '''Not GHC''' is for tickets that are not tied to a GHC release, because they are in libraries
    55      or other software that is not released with GHC.  Bugs in the "extra libraries" typically fall
    56      into this category.
    57    * '''_|_''' is for tickets that have been triaged, but we don't plan to fix them for a particular
    58      release.  This might be because the bug is low priority, or is simply too hard to fix right now.
     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, and the high priority tickets are those that we plan to fix before releasing. We will also try to fix as many of the normal and lower priority tickets as possible.
    5951
    6052 * '''Test Case''': fill in this field with the name of the test in the test suite.  Typically every bug
    6153   closed should have an appropriate test case added to the test suite.
     54
     55When 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 `_|_`.