Changes between Version 2 and Version 3 of BugSweep


Ignore:
Timestamp:
Nov 16, 2009 1:42:32 PM (6 years ago)
Author:
simonpj
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • BugSweep

    v2 v3  
    1616Here are some things to check:
    1717
    18  * Check for duplicates (Google search with "site:hackage.haskell.org"
    19    is usually better than using Trac's search).
    20 
    21  * Check that the bug hasn't already been fixed, or if it is a feature
    22    request, that it hasn't already been implemented.  If the bug has
    23    some reproduction instructions, try them out with a recent GHC and
    24    see if the bug still happens.  If the results are different, update
    25    the ticket to include that information.  If the bug does not have
    26    repro instructions, ask the submitter for more details.
    27 
    28  * Check that there is still value in having the ticket open.  If we
    29    cannot make progress without feedback from the submitter, and a
    30    long time has elapsed (e.g. 6 months), then we should close the
    31    bug.
     18 * '''All tickets''':
     19   * Check for duplicates (Google search with "site:hackage.haskell.org" is usually better than using Trac's search).
     20   * Check that the ticket is categoriesd correctly, including
     21     * the title is a good summary of the bug
     22     * platform/OS are correct
     23     * component is correct
     24     * it is on the correct milestone
     25     * the "difficulty" is a reasonable estimate
     26
     27 * '''Bugs''':
     28   * Check that the bug hasn't already been fixed.
     29   * 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. 
     30   * If the bug does not have repro instructions, ask the submitter for more details.
     31   * 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.
     32
     33 * '''Feature requests''' and '''tasks''': check that it hasnt' already been done.
    3234
    3335 * If the ticket has a patch and looks ready to go, add a comment
    3436   to the ticket to say so.
    35 
    36  * Check that the ticket is categoriesd correctly, including
    37    * the title is a good summary of the bug
    38    * platform/OS are correct
    39    * component is correct
    40    * it is on the correct milestone
    41    * the "difficulty" is a reasonable estimate
    4237
    4338Here are some [wiki:WorkingConventions#TheBugTracker more details on how we use the bug tracker].
     
    5247GHC, and hopefully someone else will pick it up.
    5348
    54 How do we track which bugs have been looked at in the sweep yet?
     49How do we track which tickets have been looked at in the sweep yet?
    5550Below is a list: just edit this page, remove a bug from the list, and
    5651look at it.  When the list is empty, we'll take a new snapshot of the
    5752database and start again.
    5853
    59 == The bugs ==
    60 
    61 Remove a bug from the top of the list:
     54== The tickets (bugs, tasks, feature requests, the lot) ==
     55
     56Remove a ticket from the top of the list:
    6257
    6358 * #17