54
edits
SeaMonkey:Triage Week Guide: Difference between revisions
Jump to navigation
Jump to search
→Whiteboard Markers: adding concrete date
Philip Chee (talk | contribs) |
(→Whiteboard Markers: adding concrete date) |
||
| 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 | * '''[CLOSEME 2011-02-01 INCO]''' for bugs that are incomplete and should be closed if the reporter doesn't add further information until yyyy-mm-dd | ||
* '''[CLOSEME | * '''[CLOSEME 2011-02-01 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 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 | ||