SeaMonkey:Triage Week Guide
- 1 Triage Week Guide
- 1.1 Goals of the Triage Week
- 1.2 How To and Requirements
- 1.3 Timetable
- 1.4 Categories
Triage Week Guide
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 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 SeaMonkey trunk build on one or more of the supported platforms for checking the bugs. Note: There are some regressions that you should know about.
- a fresh SeaMonkey profile (so that your normal work environment is not affected by tests you make)
- a BugZilla account
- an IRC client (e.g. ChatZilla, which comes with SeaMonkey but is broken in trunk builds so you need to run a SeaMonkey 2.0 in parallel, or Mibbit with "Mozilla [webirc]")
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 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 Confirming unconfirmed bugs
- read the 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. 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.
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 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 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
- [DUPEME] for bugs where an older bug report with the same issue has been seen, but cannot be found at the moment
- Screening duplicate bugs
- Thunderbird DupMe Workshop: Thunderbird:Testing/Workshops/Duplication/doc
- Confirming unconfirmed bugs
- What to do and what not to do in Bugzilla
We have three time slots on each day, so people from different parts of the world can join us on IRC:
- 1200-1400 UTC Asia / Pacific
- 1900-2100 UTC Europe / Africa / Near East
- 0100-0300 UTC North-/South America
The triage week is divided into categories for each day, so we can focus on different components
Browser usage (Monday, 2010-12-06)
All components that are related to the usage of the browser itself.
- Bookmarks & History
- Find In Page
- Location Bar
- Page Info
- Tabbed Browser
Security (Tuesday, 2010-12-07)
Security and safety related bugs.
- Passwords & Permissions
Operating System / Startup (Wednesday, 2010-12-08)
This category includes the components which directly affect the Operating System and the startup of SeaMonkey.
- Download & File Handling
- OS Integration
- Session Restore
- Startup & Profiles
MailNews (Thursday/Friday, 2010-12-09/2010-12-10)
All components related to MailNews
- MailNews: Account Configuration
- MailNews: Address Book & Contacts
- MailNews: Backend
- MailNews: Composition
- MailNews: General
- MailNews: Message Display
Help / UI (Saturday, 2010-12-11)
All components that are related to the user interface, including Help and Preferences for customizing the browser.
- UI Design
Final day (Sunday, 2010-12-12)
Sort out our "take it all" component and move the bugs to the correct components.