SeaMonkey:Triage Week: Difference between revisions
Jump to navigation
Jump to search
(initial planning steps) |
|||
| Line 1: | Line 1: | ||
= Triage Week = | |||
The problem: [https://bugzilla.mozilla.org/report.cgi?query_format=report-table&format=table&action=wrap&x_axis_field=bug_status&y_axis_field=component&product=SeaMonkey&resolution=--- our bug list] | The problem: [https://bugzilla.mozilla.org/report.cgi?query_format=report-table&format=table&action=wrap&x_axis_field=bug_status&y_axis_field=component&product=SeaMonkey&resolution=--- our bug list] | ||
| Line 5: | Line 5: | ||
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. | 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) | |||
== How to get community involved == | == 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?) | |||
* 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? | |||
== Afermath == | |||
* How can we judge the results of the triage week? | |||
Revision as of 11:29, 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?)
- 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?
Afermath
- How can we judge the results of the triage week?