Changes between Version 37 and Version 38 of WorkingConventions


Ignore:
Timestamp:
Oct 20, 2007 3:37:46 PM (8 years ago)
Author:
ross
Comment:

note on Milestone

Legend:

Unmodified
Added
Removed
Modified
  • WorkingConventions

    v37 v38  
    2727We organise our work (both bug fixing and feature requests) using the Trac bug tracker.   There are links to the bug tracker in the sidebar under "View tickets" ad "Create ticket".
    2828
    29 The following are GHC-specific policies for using the Trac bug tracking system. (See also [wiki:ReportABug the bug reporting guidelines].)
     29The following are GHC-specific policies regarding the fields of the Trac bug tracking system. (See also [wiki:ReportABug the bug reporting guidelines].)
    3030
    31  * When a bug is fixed, but the patch or patches still need to be merged to other branches, then
    32    don't close the bug, just change its type from "bug" or "task" to "merge".  Also add a list of
     31 * '''Type''': When a bug is fixed, but the patch or patches still need to be merged to other branches, then
     32   don't close the bug, just change its type from '''bug''' or '''task''' to '''merge'''.  Also add a list of
    3333   patches to be merged, and which branch to merge to, as a comment.
    3434
    35  * '''Milestones''': we have milestones for each release, and three special milestones:
     35 * '''Severity''': this is set by the submitter of the ticket, and indicates how important the issue is to
     36   them, i.e. is it preventing them from doing something altogether, or just a minor annoyance.  The
     37   severity might be reduced if we discover a workaround.
     38
     39 * '''Priority''': this field is for the GHC development team to help us prioritise what we work on.  Bugs
     40   that have a high severity will tend to be prioritised higher, as will bugs that are regressions from
     41   a previous release.
     42
     43 * '''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:
    3644   * An empty milestone field means the bug has not been triaged yet.  We don't yet know if the
    3745     ticket is a real, unique, issue.  Once this has been established, the ticket will be given
     
    4351     release.  This might be because the bug is low priority, or is simply too hard to fix right now.
    4452
    45  * '''Severity''': this is set by the submitter of the ticket, and indicates how important the issue is to
    46    them, i.e. is it preventing them from doing something altogether, or just a minor annoyance.  The
    47    severity might be reduced if we discover a workaround.
    48 
    49  * '''Priority''': this field is for the GHC development team to help us prioritise what we work on.  Bugs
    50    that have a high severity will tend to be prioritised higher, as will bugs that are regressions from
    51    a previous release.
    52 
    5353 * '''Test Case''': fill in this field with the name of the test in the test suite.  Typically every bug
    5454   closed should have an appropriate test case added to the test suite.