... | ... | @@ -20,34 +20,40 @@ Here are some things to check: |
|
|
- **All tickets**:
|
|
|
|
|
|
- Check for duplicates (Google search with "site:hackage.haskell.org" is usually better than using Trac's search).
|
|
|
- Tidy up the description: add markup if necessary, link to related information and/or other tickets
|
|
|
- Check that the ticket is categoriesd correctly, including
|
|
|
|
|
|
- the title is a good summary of the bug
|
|
|
- platform/OS are correct
|
|
|
- component is correct
|
|
|
- it is on the correct milestone
|
|
|
- the "difficulty" is a reasonable estimate
|
|
|
- it is on the correct milestone (developers only)
|
|
|
- the "difficulty" is a reasonable estimate (developers only)
|
|
|
- If the ticket has a patch
|
|
|
|
|
|
- (developers only) review the patch
|
|
|
- if it looks ready to go, add a comment to the ticket to say so.
|
|
|
|
|
|
- **Bugs**:
|
|
|
|
|
|
- Check that the bug hasn't already been fixed.
|
|
|
- Set the new "Type of Failure" field
|
|
|
- If the bug has some reproduction instructions, try them out with a recent GHC and see if the bug still happens. If the results are different, update the ticket to include that information.
|
|
|
- If the bug does not have repro instructions, ask the submitter for more details.
|
|
|
- Check that there is still value in having the ticket open. If we cannot make progress without feedback from the submitter, and a long time has elapsed (e.g. 6 months), then we should close the bug.
|
|
|
|
|
|
- **Feature requests** and **tasks**: check that it hasnt' already been done.
|
|
|
- **Feature requests** and **tasks**:
|
|
|
|
|
|
- If the ticket has a patch and looks ready to go, add a comment
|
|
|
to the ticket to say so.
|
|
|
- check that it hasn't already been done.
|
|
|
- link to related feature requests
|
|
|
|
|
|
|
|
|
Here are some [more details on how we use the bug tracker](working-conventions#the-bug-tracker).
|
|
|
|
|
|
|
|
|
For many tickets there may be nothing to do. In some cases you might
|
|
|
not know what to do: e.g. you might not know which is a good milestone
|
|
|
for a bug. In that case, you could ask a GHC developer on IRC, or
|
|
|
just make a guess; we can always correct it later. You might not be
|
|
|
Note: you don't have to do *all* of the things on the list. Doing *any* of them is good. The main thing is that every ticket gets at least looked at.
|
|
|
|
|
|
|
|
|
For many tickets there may be nothing to do: if so, just proceed to the next ticket. You might not be
|
|
|
able to reproduce the bug (because you don't have access to the right
|
|
|
platform, for instance). In that case just add a comment to the
|
|
|
ticket to note that the bug needs to be reproduced with an up to date
|
... | ... | |