SeaMonkey:Triage Week Guide: Difference between revisions

 
(2 intermediate revisions by the same user not shown)
Line 43: Line 43:
* triage bugs by trying to reproduce the issue, adding useful information and changing the status
* triage bugs by trying to reproduce the issue, adding useful information and changing the status
** try to reproduce the problem using the given steps. Do not hesitate to ask on the IRC channel!
** try to reproduce the problem using the given steps. Do not hesitate to ask on the IRC channel!
** add useful information by adding comments that explain whether the bug can be reproduced and how, or why it's not an issue anymore
** add useful information by adding comments that explain whether the bug can be reproduced and how, or why it's not an issue anymore. Please include the build identifier string from about: for the SeaMonkey version you were using.
** change the bug status according to your findings if you have the privileges, else set whiteboard markers.
** change the bug status according to your findings if you have the privileges, else set whiteboard markers.


Line 49: Line 49:
Only members with certain privileges can actually change the status of a bug. You can ask such members on the IRC channel to change the status for you or add one of the below keywords to the Whiteboard field of a bug. Members with privileges will process those bugs later then.
Only members with certain privileges can actually change the status of a bug. You can ask such members on the IRC channel to change the status for you or add one of the below keywords to the Whiteboard field of a bug. Members with privileges will process those bugs later then.


* '''[CLOSEME yyyy-mm-dd INCO]''' for bugs that are incomplete and should be closed if the reporter doesn't add further information until yyyy-mm-dd
* '''[CLOSEME 2011-02-01 INCO]''' for bugs that are incomplete and should be closed if the reporter doesn't add further information until 2011-02-01
* '''[CLOSEME yyyy-mm-dd WFM]''' for bugs that cannot be reproduced with a current SeaMonkey trunk nightly and should be closed on yyyy-mm-dd if the bug reporter doesn't say otherwise
* '''[CLOSEME 2011-02-01 WFM]''' for bugs that cannot be reproduced with a current SeaMonkey trunk nightly and should be closed on 2011-02-01 if the bug reporter doesn't say otherwise
* '''[CLOSEME INVA/WONT?]''' for bugs that could be INVALID (not an issue with SeaMonkey) or WONTFIX (final decision up to the module owner / SeaMonkey Council). The owner of the component or somebody familiar with it has to decide what to do with it
* '''[CLOSEME INVA/WONT?]''' for bugs that could be INVALID (not an issue with SeaMonkey) or WONTFIX (final decision up to the module owner / SeaMonkey Council). The owner of the component or somebody familiar with it has to decide what to do with it
* '''[DUPEME]''' for bugs where an older bug report with the same issue has been seen, but cannot be found at the moment
* '''[DUPEME]''' for bugs where an older bug report with the same issue has been seen, but cannot be found at the moment
54

edits