Changes between Version 16 and Version 17 of WorkingConventions


Ignore:
Timestamp:
Jan 8, 2007 10:46:55 AM (9 years ago)
Author:
simonmar
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • WorkingConventions

    v16 v17  
    119119   patches to be merged, and which branch to merge to, as a comment.
    120120
    121  * Milestones: we have milestones for each release, and three special milestones:
     121 * '''Milestones''': we have milestones for each release, and three special milestones:
    122122   * An empty milestone field means the bug has not been triaged yet.  We don't yet know if the
    123123     ticket is a real, unique, issue.  Once this has been established, the ticket will be given
     
    129129     release.  This might be because the bug is low priority, or is simply too hard to fix right now.
    130130
     131 * '''Severity''': this is set by the submitter of the ticket, and indicates how important the issue is to
     132   them, i.e. is it preventing them from doing something altogether, or just a minor annoyance.  The
     133   severity might be reduced if we discover a workaround.
     134
     135 * '''Priority''': this field is for the GHC development team to help us prioritise what we work on.  Bugs
     136   that have a high severity will tend to be prioritised higher, as will bugs that are regressions from
     137   a previous release.