BugSquad/Triage Guide - Revision history

FGrose at 15:27, 1 April 2010

2010-04-01T15:27:42Z

← Older revision		Revision as of 11:27, 1 April 2010
Line 1:		Line 1:
	<noinclude>{{ ~~GoogleTrans-en~~ \| es =show \| bg =show \| zh-CN =show \| zh-TW =show \| hr =show \| cs =show \| da =show \| nl =show \| fi =show \| fr =show \| de =show \| el =show \| hi =show \| it =show \| ja =show \| ko =show \| no =show \| pl =show \| pt =show \| ro =show \| ru =show \| sv =show }}{{~~TeamHeader\|BugSquad~~}}</noinclude>~~{{TOCright}}~~		<noinclude>{{TeamHeader\|BugSquad}}{{TOCright}}
			[[Category:BugSquad]]
			[[Category:HowTo]]
			</noinclude>

	== Why bug triaging is helpful? ==		== Why bug triaging is helpful? ==
Line 26:		Line 29:

	=== Find what should be changed===		=== Find what should be changed===
	Read the [[BugSquad/Triage Guide#~~Steps_of_Triaging~~]] to determine what should be changed (if anything) and how.		Read the [[BugSquad/Triage Guide#Steps of Triaging]] to determine what should be changed (if anything) and how.

	=== Ask someone to verify your changes ===		=== Ask someone to verify your changes ===
	For the first bugs we encourage you to make the changes in conjunction with a member of the ~~bugsqad~~ team [[BugSquad/Contacts#~~Squad_Members~~]]. You will find them usually at #sugar on freenode.		For the first bugs we encourage you to make the changes in conjunction with a member of the BugSquad team [[BugSquad/Contacts#Squad Members]]. You will find them usually at #sugar on freenode.

	=== Make your changes ===		=== Make your changes ===
Line 47:		Line 50:
	=== If the bug is not described well ===		=== If the bug is not described well ===

	The bug report isn't very useful if the bug isn't described well. Some people do not read the [[BugSquad/~~BugHowto~~]] or are just inexperienced. Best, is to use one of the stock answers and go to the next bug :)		The bug report isn't very useful if the bug isn't described well. Some people do not read the [[BugSquad/Bug Report]], [[olpc:Reporting bugs]], or are just inexperienced. Best, is to use one of the stock answers and go to the next bug :)

	=== If the bug is in an obsolete version of the application ===		=== If the bug is in an obsolete version of the application ===
Line 59:		Line 62:
	=== Severity of the bug ===		=== Severity of the bug ===
	Verify that the severity of the bug is set correctly. What you should not try to set is the milestone and the priority of the bugs, this is the duty of the component maintainer. (Please refer to [[BugSquad/Status_Fields#Severity_.28Default.3DUnspecified.29\|Severity]] for a definition of the severity fields.)		Verify that the severity of the bug is set correctly. What you should not try to set is the milestone and the priority of the bugs, this is the duty of the component maintainer. (Please refer to [[BugSquad/Status_Fields#Severity_.28Default.3DUnspecified.29\|Severity]] for a definition of the severity fields.)


	~~[[Category:BugSquad]]~~
	~~[[Category:HowTo]]~~

Sascha silbe: dev.sugarlabs.org -> bugs.sugarlabs.org

2010-03-10T12:52:08Z

dev.sugarlabs.org -> bugs.sugarlabs.org

← Older revision		Revision as of 08:52, 10 March 2010
Line 10:		Line 10:
	== How to get up to speed ==		== How to get up to speed ==
	=== Create a trac account ===		=== Create a trac account ===
	* Create a trac account at [~~http~~://~~dev~~.sugarlabs.org/register ~~dev~~.sugarlabs.org].		* Create a trac account at [https://bugs.sugarlabs.org/register bugs.sugarlabs.org].

	=== Join the sugar-devel mailing list ===		=== Join the sugar-devel mailing list ===
Line 23:		Line 23:
	== Triaging ==		== Triaging ==
	=== Pick a bug ===		=== Pick a bug ===
	Use the tracker to ~~create a query http~~://~~dev~~.sugarlabs.org/query. This for example creates a query for [~~http~~://~~dev~~.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=sugar&order=priority&col=id&col=summary&col=status&col=type&col=priority all open sugar bugs]. Choose one you want to triage and read it carefully.		Use the tracker to [https://bugs.sugarlabs.org/query create a query]. This for example creates a query for [https://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=sugar&order=priority&col=id&col=summary&col=status&col=type&col=priority all open sugar bugs]. Choose one you want to triage and read it carefully.

	=== Find what should be changed===		=== Find what should be changed===

Erikos: /* Why bug triaging is helpful? */

2010-03-01T18:57:37Z

Why bug triaging is helpful?

← Older revision		Revision as of 14:57, 1 March 2010
Line 6:		Line 6:
	* Verify that the bug is filed against the correct component		* Verify that the bug is filed against the correct component
	* Verify that the bug has the correct software version field		* Verify that the bug has the correct software version field
	* Verify the ~~priority~~ of the bug		* Verify the severity of the bug

	== How to get up to speed ==		== How to get up to speed ==

Walter: /* Severity of the bug */

2010-03-01T17:24:51Z

Severity of the bug

← Older revision		Revision as of 13:24, 1 March 2010
Line 58:		Line 58:

	=== Severity of the bug ===		=== Severity of the bug ===
	Verify that the severity of the bug is set correctly. What you should not try to set is the milestone and the priority of the bugs, this is the duty of the component maintainer.		Verify that the severity of the bug is set correctly. What you should not try to set is the milestone and the priority of the bugs, this is the duty of the component maintainer. (Please refer to [[BugSquad/Status_Fields#Severity_.28Default.3DUnspecified.29\|Severity]] for a definition of the severity fields.)


	[[Category:BugSquad]]		[[Category:BugSquad]]
	[[Category:HowTo]]		[[Category:HowTo]]

Cjl: moved Walter is a wanker 7/Triage Guide to BugSquad/Triage Guide over redirect: revert

2010-02-25T00:16:07Z

moved Walter is a wanker 7/Triage Guide to BugSquad/Triage Guide over redirect: revert

← Older revision	Revision as of 20:16, 24 February 2010
(No difference)

Faggot: moved BugSquad/Triage Guide to Walter is a wanker 7/Triage Guide: Walter is a wanker

2010-02-24T23:46:34Z

moved BugSquad/Triage Guide to Walter is a wanker 7/Triage Guide: Walter is a wanker

← Older revision	Revision as of 19:46, 24 February 2010
(No difference)

Patrol: moved Walter is a wanker 11/Triage Guide to BugSquad/Triage Guide over redirect: revert

2010-02-24T01:34:15Z

moved Walter is a wanker 11/Triage Guide to BugSquad/Triage Guide over redirect: revert

← Older revision	Revision as of 21:34, 23 February 2010
(No difference)

Page move vandal: moved BugSquad/Triage Guide to Walter is a wanker 11/Triage Guide: Walter is a wanker

2010-02-24T00:20:47Z

moved BugSquad/Triage Guide to Walter is a wanker 11/Triage Guide: Walter is a wanker

← Older revision	Revision as of 20:20, 23 February 2010
(No difference)

Dfarning: fix camelcase links

2009-04-03T19:30:07Z

fix camelcase links

← Older revision		Revision as of 15:30, 3 April 2009
Line 35:		Line 35:

	== Steps of Triaging ==		== Steps of Triaging ==
	These are some notes how to triage the bugs in detail. In all the cases you can find the matching stock response at [[BugSquad/Triage Guide/~~StockResponses~~]].		These are some notes how to triage the bugs in detail. In all the cases you can find the matching stock response at [[BugSquad/Triage Guide/Stock Responses]].

	=== Verify that the bug is not a duplicate ===		=== Verify that the bug is not a duplicate ===

Dfarning: fix camelcase links

2009-04-03T19:26:40Z

fix camelcase links

← Older revision		Revision as of 15:26, 3 April 2009
Line 26:		Line 26:

	=== Find what should be changed===		=== Find what should be changed===
	Read the [[BugSquad/~~TriageGuide~~#Steps_of_Triaging]] to determine what should be changed (if anything) and how.		Read the [[BugSquad/Triage Guide#Steps_of_Triaging]] to determine what should be changed (if anything) and how.

	=== Ask someone to verify your changes ===		=== Ask someone to verify your changes ===
Line 35:		Line 35:

	== Steps of Triaging ==		== Steps of Triaging ==
	These are some notes how to triage the bugs in detail. In all the cases you can find the matching stock response at [[BugSquad/~~TriageGuide~~/StockResponses]].		These are some notes how to triage the bugs in detail. In all the cases you can find the matching stock response at [[BugSquad/Triage Guide/StockResponses]].

	=== Verify that the bug is not a duplicate ===		=== Verify that the bug is not a duplicate ===