SeaMonkey:Triage Week: Difference between revisions
Jump to navigation
Jump to search
m (→Afermath) |
|||
| Line 19: | Line 19: | ||
== How to get the community involved? == | == How to get the community involved? == | ||
* Post in the newsgroups (mozilla.dev.apps.seamonkey and mozilla.support.seamonkey) | * Post in the newsgroups (mozilla.dev.apps.seamonkey and mozilla.support.seamonkey) | ||
* Blogposts to appear at planet.m.o (SeaMonkey blog, KaiRo?, anyone else?) | * Blogposts to appear at planet.m.o (SeaMonkey blog, KaiRo?, anyone else? QMO?) | ||
* Post at | * Post at MozillaZine | ||
* Any other ways to announce it? | * Any other ways to announce it? | ||
Revision as of 22:28, 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.
Planning
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
- Who decides about what bugs are INVALID/WONTFIX? Ask component owners?
- What to do with incomplete bugs? Ask the bug reporter for further information and set a closeme-date?
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 IRC channel for questions (name suggestion #seamonkey.triage)
- 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?