SeaMonkey:Triage Week - Revision history

Aqualon: /* Aftermath */

2010-12-14T14:15:40Z

Aftermath

← Older revision		Revision as of 14:15, 14 December 2010
Line 52:		Line 52:

	== Aftermath ==		== Aftermath ==
	* ~~How can we judge the results of the triage week?~~		* See [https://wiki.mozilla.org/SeaMonkey:StatusMeetings:2010-12-14#Feature_List.2C_Planning Status Meeting 2010-12-14] report.

	= '''Categories''' =		= '''Categories''' =

Aqualon: /* Categories */

2010-12-05T19:50:24Z

Aqualon: Added link to the triage week guide

2010-12-02T20:53:08Z

Added link to the triage week guide

← Older revision		Revision as of 20:53, 2 December 2010
Line 4:		Line 4:

	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.

			= ''' How to help? ''' =

			'''You can find detailed information on how to participate and the schedule of the triage week on the [[SeaMonkey:Triage_Week_Guide\|Triage Week Guide]] page.'''

	= '''Planning''' =		= '''Planning''' =

Aqualon: /* How can we support triagers? */

2010-11-30T13:57:40Z

How can we support triagers?

← Older revision		Revision as of 13:57, 30 November 2010
Line 43:		Line 43:

	== How can we support triagers? ==		== How can we support triagers? ==
	* ~~Have an extra IRC channel for questions (name suggestion:~~ #seamonkey~~.triage) or use #bugday?~~		* Use #seamonkey as support channel on IRC
	* 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?		* 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?		* 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?

Aqualon: /* Open Questions */

2010-11-30T13:09:17Z

Open Questions

← Older revision		Revision as of 13:09, 30 November 2010
Line 32:		Line 32:
	** => see [[SeaMonkey:Triage_Week#Resolving_Bugs]]		** => see [[SeaMonkey:Triage_Week#Resolving_Bugs]]
	* How much time to give bug reporters for delivering further information?		* 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.		** -> We probably can't expect much to be done during Christmas holiday season, so using 2011-02-01 as closeme date could be reasonable and easy to remember.
	* 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 mentioned the 3 timeslots the Thunderbird guys will be using on Dec. 2 for their "Finding dupes" workshop, namely Asia/Pacific (1200-1400 UTC), Europe / Africa / Near East (1900-2100 UTC) and the Americas [from Alaska to Tierra del Fuego ;-) ] (0100-0300 UTC). We might do something similar.		** -> Tony mentioned the 3 timeslots the Thunderbird guys will be using on Dec. 2 for their "Finding dupes" workshop, namely Asia/Pacific (1200-1400 UTC), Europe / Africa / Near East (1900-2100 UTC) and the Americas [from Alaska to Tierra del Fuego ;-) ] (0100-0300 UTC). We might do something similar.

Tonymec: /* Open Questions */ give credit where credit is due

2010-11-30T10:26:05Z

Open Questions: give credit where credit is due

← Older revision		Revision as of 10:26, 30 November 2010
Line 34:		Line 34:
	** -> We probably can't expect much to be done during Christmas holiday season, so using 2011-01-15 as closeme date could be reasonable.		** -> 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).		** -> Tony mentioned the 3 timeslots the Thunderbird guys will be using on Dec. 2 for their "Finding dupes" workshop, namely Asia/Pacific (1200-1400 UTC), Europe / Africa / Near East (1900-2100 UTC) and the Americas [from Alaska to Tierra del Fuego ;-) ] (0100-0300 UTC). We might do something similar.

	== How to get the community involved? ==		== How to get the community involved? ==

Tonymec: /* Resolving Bugs */

2010-11-30T09:07:59Z

Resolving Bugs

← Older revision		Revision as of 09:07, 30 November 2010
Line 162:		Line 162:
	*** [[Modules/MailNews Core]]		*** [[Modules/MailNews Core]]
	** [https://spreadsheets.google.com/ccc?key=pcR-hFir9x0Pn-TxV3j2Zbg&hl=en&pli=1#gid=0 The "Bugzilla Components / Modules" Google spreadsheet]		** [https://spreadsheets.google.com/ccc?key=pcR-hFir9x0Pn-TxV3j2Zbg&hl=en&pli=1#gid=0 The "Bugzilla Components / Modules" Google spreadsheet]
	** [http://www.mozilla.org/owners.html The Mozilla list of owners & peers (somewhat outdated?)]		<!-- ** [http://www.mozilla.org/owners.html The Mozilla list of owners & peers (somewhat outdated?)] ---- this one is now a redirect to "Modules", listed above -->
	* Beware that some of these documents list for some people email addresses different from their Bugzilla address-of-record.		* Beware that some of these documents list for some people email addresses different from their Bugzilla address-of-record.

	'''DUPEME'''		'''DUPEME'''
	This marker can be used for bugs where an older bug report with the same issue has been seen, but can't be found at the moment.		This marker can be used for bugs where an older bug report with the same issue has been seen, but can't be found at the moment.

Tonymec: /* Resolving Bugs */

2010-11-30T08:35:19Z

Resolving Bugs

← Older revision		Revision as of 08:35, 30 November 2010
Line 154:		Line 154:
	'''[CLOSEME INVA/WONT?]'''		'''[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.		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.
			* The following documents can help you find who are the owner and peers of a given component:
			** [http://www.seamonkey-project.org/dev/project-areas The SeaMonkey "Project Areas" page]
			** The MozillaWiki [[Modules]] page, and in particular:
			*** [[Modules/SeaMonkey]]
			*** [[Modules/Core]]
			*** [[Modules/Toolkit]]
			*** [[Modules/MailNews Core]]
			** [https://spreadsheets.google.com/ccc?key=pcR-hFir9x0Pn-TxV3j2Zbg&hl=en&pli=1#gid=0 The "Bugzilla Components / Modules" Google spreadsheet]
			** [http://www.mozilla.org/owners.html The Mozilla list of owners & peers (somewhat outdated?)]
			* Beware that some of these documents list for some people email addresses different from their Bugzilla address-of-record.

	'''DUPEME'''		'''DUPEME'''
	This marker can be used for bugs where an older bug report with the same issue has been seen, but can't be found at the moment.		This marker can be used for bugs where an older bug report with the same issue has been seen, but can't be found at the moment.

Tonymec: /* Resolving Bugs */ typo

2010-11-30T08:05:18Z

Resolving Bugs: typo

← Older revision		Revision as of 08:05, 30 November 2010
Line 156:		Line 156:

	'''DUPEME'''		'''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.		This marker can be used for bugs where an older bug report with the same issue has been seen, but can't be found at the moment.

Aqualon: Adding information about "resolving bugs"

2010-11-29T11:32:29Z

Adding information about "resolving bugs"

← Older revision		Revision as of 11:32, 29 November 2010
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.

@@ Line 55: / Line 55: @@
 = '''Categories''' =
-== Browser usage (Monday, 2010-12-06) ==
+For the actual categories see [[SeaMonkey:Triage_Week_Guide#Categories|Triage Week Guide]].
 == Project ==