Changes between Version 39 and Version 40 of WorkingConventions/FixingBugs


Ignore:
Timestamp:
Nov 16, 2017 10:06:36 AM (2 years ago)
Author:
pcarbonn
Comment:

+ link to DocChanges

Legend:

Unmodified
Added
Removed
Modified
  • WorkingConventions/FixingBugs

    v39 v40  
    1111= How to contribute a patch to GHC =
    1212
    13 Here's how to submit a bug fix to GHC. For [wiki:WorkingConventions/AddingFeatures adding features], there are a few extra steps to follow.
     13Here's how to submit a bug fix to GHC. For [wiki:WorkingConventions/DocumentationChanges changing the documentation], there is a simpler procedure.  For [wiki:WorkingConventions/AddingFeatures adding features], there are a few extra steps to follow.
    1414
    1515 0. '''Make sure the bug is in Trac'''.  Usually it is (that's why you are working on it), but if it's a bug you have found yourself, add it to Trac before you start work. It's important to have a ticket, because it makes sure that the bug report, discussion about the fix, the regression test that checks it, and the eventual conclusion, are all recorded together.  Comments in the code can refer to the ticket (e.g. `See Trac #2382 for an example`). And so on.  If there's no ticket, there is every chance that it'll get lost.[[BR]][[BR]]