Changes between Version 12 and Version 13 of ReportABug


Ignore:
Timestamp:
Feb 4, 2011 1:02:41 PM (3 years ago)
Author:
simonmar
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ReportABug

    v12 v13  
    3030The Trac bug report system has various fields. Here's how to fill them in: 
    3131 
    32  * '''CC'''.  If you are only logged in as ''guest'' then please consider including your email address (using a comma or space as separator, not a semicolon). That way we can ask you questions, and you'll get email from Trac when something happens to your bug. 
    33  
    34  * '''Short summary'''.  This is what appears in one-bug-per line lists, so try to make it as informative as you can. 
     32 * '''Short summary'''.  This is what appears in one-bug-per line lists, so try to make it as informative as you can. A snippet of the error message, if there is one, usually makes a good summary. 
    3533 
    3634 * '''Type''' says what kind of Trac ticket this is: 
     
    3937   * '''proposal''': reserved for use with the [http://www.haskell.org/haskellwiki/Library_submissions Library submissions] process 
    4038   * '''task''' (for use by GHC developers only): something we intend to do sometime 
    41    * '''merge''' (for use by GHC developers only): job done, but must be merged to stable branch 
    4239  
    43  * '''Severity'''.  How much this bug matters to you. 
     40 * '''Type of failure''': the nature of the failure (compile-time crash, incorrect result, etc.).  This allows us to prioritize important bugs. 
    4441 
    4542 * '''Full description'''.  This is where you describe your bug in details.  See "What information to provide" below.  Use the [wiki:TracWikiMisc wiki markup] in your description, especially `{{{` ... `}}}` brackets to mark up literal code. 
    4643 
     44 * '''CC'''.  If you are only logged in as ''guest'' then please consider including your email address (using a comma or space as separator, not a semicolon). That way we can ask you questions, and you'll get email from Trac when something happens to your bug. 
     45 
    4746 * '''Component''', '''Version''', '''Operating system''', '''Architecture''' all help to describe the setup that failed. Please pay particular attention to '''version''', which is the version of GHC that you are running. 
    4847 
    49  * '''Priority''' and '''Milestone'''.  Please do  not fill in these fields.   We use them to organise our priorities.  The '''severity''' field lets you say how important the bug is to you. 
    50  
    51   * '''Assign to''', '''Difficulty''', '''Test case'''.  For use by GHC developers; please don't fill these in. 
     48  * '''Priority''', '''Milestone''', '''Assign to''', '''Difficulty''', '''Test case''', '''Blocking''', '''Blocked by''':  these are all for use by GHC developers; please don't fill these in. 
    5249 
    5350See also [wiki:WorkingConventions GHC working conventions].