54
edits
SeaMonkey:Triage Week: Difference between revisions
Adding information about "resolving bugs"
(Adding information about "resolving bugs") |
|||
| Line 20: | Line 20: | ||
== Open Questions == | == Open Questions == | ||
* Should we limit it to a certain component (last bug day: General), only new bugs, ..., or a different one each day? | * Should we limit it to a certain component (last bug day: General), only new bugs, ..., or a different one each day? | ||
** Limitation to certain components is a good idea, probably we should make it dependent on when people familiar with a component have time to be on IRC. | ** <strike>Limitation to certain components is a good idea, probably we should make it dependent on when people familiar with a component have time to be on IRC.</strike> | ||
** => see [[SeaMonkey:Triage_Week#Categories]] | ** => see [[SeaMonkey:Triage_Week#Categories]] | ||
* Who decides about what bugs are INVALID/WONTFIX? | * Who decides about what bugs are INVALID/WONTFIX? | ||
** Ask component owners? Ask experienced community members ("champions")? | ** <strike>Ask component owners? Ask experienced community members ("champions")? | ||
** -> Use a wontfix? whiteboard marker? | ** -> Use a wontfix? whiteboard marker? | ||
** -> Use needs-resolution whiteboard marker? | ** -> Use needs-resolution whiteboard marker?</strike> | ||
** => see [[SeaMonkey:Triage_Week#Resolving_Bugs]] | |||
* What to do with incomplete bugs? | * What to do with incomplete bugs? | ||
** Ask the bug reporter for further information and set a closeme-date? | ** <strike>Ask the bug reporter for further information and set a closeme-date? | ||
** -> Use a closeme whiteboard marker | ** -> Use a closeme whiteboard marker</strike> | ||
** => see [[SeaMonkey:Triage_Week#Resolving_Bugs]] | |||
* How much time to give bug reporters for delivering further information? | |||
** -> We probably can't expect much to be done during Christmas holiday season, so using 2011-01-15 as closeme date could be reasonable. | |||
* 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? | ||
** -> Tony suggested to do 3 timeslots for Asian/Pacific (1200-1400 UTC), Europe (1900-2100 UTC) and American (0100-0300 UTC). | |||
== How to get the community involved? == | == How to get the community involved? == | ||
| Line 136: | Line 141: | ||
[https://bugzilla.mozilla.org/report.cgi?x_axis_field=bug_status&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&product=SeaMonkey&component=Composer&component=Sidebar&longdesc_type=allwordssubstr&longdesc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&resolution=---&emailtype1=substring&email1=&emailtype2=substring&email2=&bug_id_type=anyexact&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0= Bugzilla report] [https://bugzilla.mozilla.org/buglist.cgi?action=wrap&bug_file_loc=&bug_file_loc_type=allwordssubstr&bug_id=&bug_id_type=anyexact&chfieldfrom=&chfieldto=Now&chfieldvalue=&email1=&email2=&emailtype1=substring&emailtype2=substring&field0-0-0=noop&keywords=&keywords_type=allwords&longdesc=&longdesc_type=allwordssubstr&product=SeaMonkey&resolution=---&short_desc=&short_desc_type=allwordssubstr&status_whiteboard=&status_whiteboard_type=allwordssubstr&type0-0-0=noop&value0-0-0=&votes=&=&bug_status=UNCONFIRMED&component=Composer&component=Sidebar 108 UNCO] [https://bugzilla.mozilla.org/buglist.cgi?action=wrap&bug_file_loc=&bug_file_loc_type=allwordssubstr&bug_id=&bug_id_type=anyexact&chfieldfrom=&chfieldto=Now&chfieldvalue=&email1=&email2=&emailtype1=substring&emailtype2=substring&field0-0-0=noop&keywords=&keywords_type=allwords&longdesc=&longdesc_type=allwordssubstr&product=SeaMonkey&resolution=---&short_desc=&short_desc_type=allwordssubstr&status_whiteboard=&status_whiteboard_type=allwordssubstr&type0-0-0=noop&value0-0-0=&votes=&=&bug_status=NEW&component=Composer&component=Sidebar 186 NEW] | [https://bugzilla.mozilla.org/report.cgi?x_axis_field=bug_status&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&product=SeaMonkey&component=Composer&component=Sidebar&longdesc_type=allwordssubstr&longdesc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&resolution=---&emailtype1=substring&email1=&emailtype2=substring&email2=&bug_id_type=anyexact&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0= Bugzilla report] [https://bugzilla.mozilla.org/buglist.cgi?action=wrap&bug_file_loc=&bug_file_loc_type=allwordssubstr&bug_id=&bug_id_type=anyexact&chfieldfrom=&chfieldto=Now&chfieldvalue=&email1=&email2=&emailtype1=substring&emailtype2=substring&field0-0-0=noop&keywords=&keywords_type=allwords&longdesc=&longdesc_type=allwordssubstr&product=SeaMonkey&resolution=---&short_desc=&short_desc_type=allwordssubstr&status_whiteboard=&status_whiteboard_type=allwordssubstr&type0-0-0=noop&value0-0-0=&votes=&=&bug_status=UNCONFIRMED&component=Composer&component=Sidebar 108 UNCO] [https://bugzilla.mozilla.org/buglist.cgi?action=wrap&bug_file_loc=&bug_file_loc_type=allwordssubstr&bug_id=&bug_id_type=anyexact&chfieldfrom=&chfieldto=Now&chfieldvalue=&email1=&email2=&emailtype1=substring&emailtype2=substring&field0-0-0=noop&keywords=&keywords_type=allwords&longdesc=&longdesc_type=allwordssubstr&product=SeaMonkey&resolution=---&short_desc=&short_desc_type=allwordssubstr&status_whiteboard=&status_whiteboard_type=allwordssubstr&type0-0-0=noop&value0-0-0=&votes=&=&bug_status=NEW&component=Composer&component=Sidebar 186 NEW] | ||
= Resolving Bugs = | |||
The goal is to resolve bugs, i.e. mark valid UNCO bugs as NEW, dupe them against known bugs and so on. For those bugs which are not clear, there are several whiteboard markers that can be used. | |||
'''[CLOSEME yyyy-mm-dd INCO]''' | |||
The bug report is incomplete and should be closed if the reporter doesn't add further information until yyyy-mm-dd. | |||
'''[CLOSEME yyyy-mm-dd WFM]''' | |||
The bug can't be reproduced with a current SeaMonkey nightly and should be closed on yyyy-mm-dd if the bug reporter doesn't say otherwise. | |||
'''[CLOSEME INVA/WONT?]''' | |||
This marker can be used for bugs that could be INVALID or WONTFIX and the owner of the component or somebody familiar with it has to decide what to do with it. | |||
'''DUPEME''' | |||
This marker can be used for bugs where am older bug report with the same issue has been seen, but can't be found at the moment. | |||