Revision as of 22:50, 15 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.

Documents on Bug Days:

Suggested Date: Week from 2010-11-29 to 2010-12-05 (CW 48)

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

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")?
What to do with incomplete bugs?
- Ask the bug reporter for further information and set a closeme-date?
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?

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?

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?

@@ Line 19: / Line 19: @@
 == Open Questions ==
-* Should we limit it to a certain component (last bug day: General), only new bugs, ...?
+* 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")?