|Version 1 (modified by 9 years ago) (diff),|
How to submit a bug fix
Please help us fix bugs in GHC! GHC is so large, and is used in such diverse ways by so many people, that we really need your help in fixing bugs, especially those that show up in specialised situations.
Here's how to go about it.
- 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.
- Take ownership of the bug in Trac, by using the "Action" chunk at the bottom of the Trac bug display (you need to be logged in to see it), and putting your name in the "reassign to" box. This makes sure that two people don't work on the same bug. If you later decide you can't do it after all, remove your name.
- Add a test case in the regression-test suite that shows up the bug.
- Put the name of the test in the "Test Case" field of the Trac report.
- Put a reference to the Trac bug e.g. "Trac #1466" in a comment in the test case.
- Follow our coding conventions
- Comment your fix in the source code, and include a reference to the bug ticket number, e.g. "
#1466" (this helps when grepping for the fix later). It is often helpful to give a small example code fragment that demonstrates the need for your fix. This isn't always relevant; sometimes you are fixing a plain error, but often it's more subtle than that.
- Follow our convention for naming patches: WorkingConventions/Darcs.
- If you don't have commit permission for the repository,
- Use 'darcs send' to create a patch bundle
- Attach the patch bundle to the Trac bug report
- Add a comment to the Trac bug report to say what you've done
- Change the owner of the bug to the GHC support engineer (currently 'igloo') This shifts responsibility to the GHC team to review and commit your patch.
Then have a beer on us. We are truly grateful.