639
edits
SeaMonkey:Triage Week Guide: Difference between revisions
Jump to navigation
Jump to search
filled Goals, HowTo and Requirements sections
(filled Goals, HowTo and Requirements sections) |
|||
| Line 3: | Line 3: | ||
== '''Goals of the Triage Week''' == | == '''Goals of the Triage Week''' == | ||
* Identify and close bugs that are not an issue anymore with the latest version of SeaMonkey | |||
* Confirm bugs that can be reproduced and that are an issue with SeaMonkey itself | |||
* Improve bugs that lack information | |||
== '''How To and Requirements''' == | == '''How To and Requirements''' == | ||
=== How to Achieve the Goals === | |||
... | * Identify and close bugs | ||
** if they have been fixed through another bug, mark them as a duplicate of that other bug | |||
** else mark them WORKSFORME (WFM) | |||
* Confirm bugs | |||
** try to find another, older bug about the same issue that is already in the NEW state, then mark the bug you're looking at as a duplicate of the other bug | |||
** if you cannot find another bug or yours is more precise, confirm it by changing its status to NEW | |||
* Improve bugs | |||
** add comments with information that helps reproducing and narrowing down the actual issue | |||
** move bugs to components that better match the problem at hand | |||
=== What You Need === | |||
* a [http://www.seamonkey-project.org/dev/nightly SeaMonkey trunk build] on one or more of the supported platforms | |||
* a [http://kb.mozillazine.org/Profile_manager fresh SeaMonkey profile] (so that your normal work environment is not affected by tests you make) | |||
* a [https://bugzilla.mozilla.org/createaccount.cgi BugZilla account] | |||
* an IRC client (e.g. [https://addons.mozilla.org/seamonkey/addon/16/ ChatZilla], which comes with SeaMonkey) | |||
=== What To Do === | |||
* log into IRC channel #seamonkey on moznet | |||
*# open ChatZilla by choosing "IRC Chat" from the Window menu | |||
*# click the "moznet" link in the window that opens | |||
*# type "/join #seamonkey" (without the quotation marks) and press Enter | |||
*# click the button in the lower left, choose "Change nickname..." and enter a name that suits you | |||
*# introduce yourself briefly. | |||
* log into [https://bugzilla.mozilla.org/ BugZilla] using your account so that you can comment on bugs | |||
* get started by looking at bugs that need triage | |||
*# follow today's UNCO link (see below, under Categories) | |||
*# open any bug that looks like it might need triage (e.g. old, or imprecise summary) | |||
*# read the article on [https://developer.mozilla.org/en/Confirming_unconfirmed_bugs Confirming unconfirmed bugs] | |||
*# read the [http://developer.mozilla.org/en/Bug_writing_guidelines Bug Writing Guideline] to understand what a good bug report should contain | |||
*# ask in the IRC channel if you have questions or lack information or privileges. | |||
* 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! | |||
** add useful information by adding comments that explain whether the bug can be reproduced and how, or why it's not an issue anymore | |||
** change the bug status according to your findings if you have the privileges, else set whiteboard markers. | |||
=== Whiteboard Markers === | |||
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 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 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 | |||
== '''Timetable''' == | == '''Timetable''' == | ||