8,288
edits
Changes
Jump to navigation
Jump to search
Line 1:
Line 1: − + + + + Line 10:
Line 13: − + Line 23:
Line 26: − + − + − + Line 47:
Line 50: − + Line 59:
Line 62: − − − [[Category:BugSquad]] − [[Category:HowTo]]
no edit summary
<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? ==
== 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 ===
== 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===
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 ===
=== 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 ===
=== 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.)