SeaMonkey:Triage Week: Difference between revisions
Jump to navigation
Jump to search
| Line 22: | Line 22: | ||
* Who decides about what bugs are INVALID/WONTFIX? | * Who decides about what bugs are INVALID/WONTFIX? | ||
** Ask component owners? Ask experienced community members ("champions")? | ** Ask component owners? Ask experienced community members ("champions")? | ||
** -> Use a wontfix? whiteboard marker | |||
* What to do with incomplete bugs? | * What to do with incomplete bugs? | ||
** Ask the bug reporter for further information and set a closeme-date? | ** Ask the bug reporter for further information and set a closeme-date? | ||
** -> Use a closeme whiteboard marker | |||
* Do we have the man power to do a whole bug day or should we announce a certain time window where champions are likely to be present? | * Do we have the man power to do a whole bug day or should we announce a certain time window where champions are likely to be present? | ||
Revision as of 13:49, 16 November 2010
Triage Week
The problem: our bug list
The idea: do a triage week to get the number of UNCONFIRMED bugs down and see which of the NEW bugs are still an issue.
Planning
Documents on Bug Days:
When?
Suggested Date: Week from 2010-11-29 to 2010-12-05 (CW 48)
Goals
- Resolve bugs which aren't an issue anymore
- Dupe bugs against the bugs with the fixes
- Mark UNCO bugs that can be reproduced as NEW
Open Questions
- Should we limit it to a certain component (last bug day: General), only new bugs, ..., or a different one each day?
- Who decides about what bugs are INVALID/WONTFIX?
- Ask component owners? Ask experienced community members ("champions")?
- -> Use a wontfix? whiteboard marker
- What to do with incomplete bugs?
- Ask the bug reporter for further information and set a closeme-date?
- -> Use a closeme whiteboard marker
- Do we have the man power to do a whole bug day or should we announce a certain time window where champions are likely to be present?
How to get the community involved?
- Post in the newsgroups (mozilla.dev.apps.seamonkey and mozilla.support.seamonkey)
- Blogposts to appear at planet.m.o (SeaMonkey blog, KaiRo?, anyone else? QMO?)
- Post at MozillaZine
- Any other ways to announce it?
How can we support triagers?
- Have an extra IRC channel for questions (name suggestion: #seamonkey.triage) or use #bugday?
- What extra resources do we need? Are links to QA/Triage and Thunderbird:Bug_Triage sufficient? Do we have to describe those steps specific for SeaMonkey on an extra page?
- Who can give canconfirm/editbugs rights to people who want to contribute? Or should devs resolve the bugs if somebody without those rights wants to help?
Aftermath
- How can we judge the results of the triage week?