Difference between revisions of "BugSquad"

From Sugar Labs
Jump to: navigation, search
m (added additional Content to Edit)
(Obsolete)
 
(63 intermediate revisions by 15 users not shown)
Line 1: Line 1:
The BugSquad to is the Quality Assurance (QA) team for Sugar. We test programs, work with downstream distributions and upstream applications to ensure good good bug and patch flow, triage bug reports, and manage the trac bug database.
+
{{Obsolete|No longer needed, just use Github issue tracker and let the repo Watchers handle things}}
 +
<noinclude>{{TeamHeader|BugSquad}}
 +
[[Category:BugSquad]]
 +
[[Category:Team]]
 +
</noinclude>
 +
== About ==
 +
The Sugar Labs BugSquad keeps track of current bugs in the Sugar software and tries to make sure that bugs are triaged and handled correctly. The team does not do testing itself. This is done by the downstream projects shipping Sugar. See [[BugSquad/Testing|testing]].
  
editors note: Currently, this page is an outline for developing an outline of the BugSquad's responsibilityGradually, the outline will become the bugsquad wiki page hierarchy.   
+
You need only be interested in the programming process to be in the BugSquad; in fact it is a great way to return something to the Sugar community if you cannot programIf you have an interest in the programming and development process, you can learn a great deal from the communications of those involvedHowever, see this thread for what can happen if insufficient respect and deference is applied: http://www.mail-archive.com/devel@lists.laptop.org/msg18897.html.
  
= What We Do =
+
The squad is modeled on the GNOME BugSquad: https://webstats.gnome.org/Bugsquad/
  
== Testing Sugar ==
+
== How bugs are tracked ==
  
====Teaching Users How to File Good Bugreports====
+
* We use [http://trac.edgewall.org/ trac] to keep track of bugs in the Sugar software. The Sugar Labs trac instance can be found at [http://bugs.sugarlabs.org bugs.sugarlabs.org].
Users are often the best source of good [[BugSquad/Testing#Filing Good Bug Reports|bug reports]].
+
* See [[BugSquad/Bug Report]] for an introduction to bug reporting.
 +
* Other Linux distributions where Sugar runs have their own [[BugSquad/Upstreaming_bugs|upstream]] bug tracking systems.
  
====Teaching Bug Reporters How to Follow Up on Bugreports====
+
== Upstream bugs ==
Many bugreports rot because of lack of [[BugSquad/Testing# Following Up on Bug Reports|follow up]] from reporters.
 
  
====Creating Best Practices for Developer Testing====
+
When you find a bug in a package we do not directly maintain, please report it [[BugSquad/Upstreaming_bugs|upstream]]
  
====Coordinate with Release Managers to Develop Pre-release test strategies====
+
== How to join the squad ==
 +
As mentioned above, virtually anyone can be helpful. Best way to get started is by reading the [[BugSquad/Triage Guide]] and to join us at #sugar on irc.freenode.net.
  
== Working with Distributions ==
+
== Subpages ==
Good Communication with downstream distributions is essential for receiving bug reports and patches from outside developers.
 
  
==== Create Policies for Accepting Bug Reports and Patches from Downstream ====
+
{{Special:PrefixIndex/BugSquad/}}
 
+
{{Special:PrefixIndex/Testing}}
==== Develop Patch Management Policies ====
 
As a new project, Sugar is in a unique position of developing patch management policies based on the best practices of other similar projects.
 
 
 
== Working with Application Developers ==
 
 
 
== Triaging Bug Reports ==
 
 
 
== Managing the Bug Database ==
 
 
 
= Quicklinks =
 
 
 
== Open Tickets ==
 
 
 
Here is a link to the current open tickets for Sugar [http://dev.laptop.org/query?status=assigned&status=new&status=reopened&group=component&component=sugar&order=priority].
 
 
 
== New Tickets ==
 
 
 
Here is a link to the page for opening a new ticket [http://dev.laptop.org/newticket] (Note: you need to be logged in to the Trac system to post a ticket).
 
 
 
= Content to Edit =
 
This section is a temporary placeholder to links that should be incorporated into the BugSquad hierarchy.
 
* [[BugSquad/ContentToEdit/TriageTeam|TriageTeam]]
 
* [[BugSquad/ContentToEdit/Triage|Triage]]
 
* [[BugSquad/ContentToEdit/TestCases|TestCases]]
 
* [[BugSquad/ContentToEdit/BugReport|BugReport]]
 

Latest revision as of 16:21, 14 May 2016

Stop hand.png NOTE:
The content of this page is considered
DEPRECATED and OBSOLETE
It is preserved for historical research, along with its talk page.

No longer needed, just use Github issue tracker and let the repo Watchers handle things

Team Home   ·   Join   ·   Contacts   ·   Resources   ·   FAQ   ·   Roadmap   ·   To Do   ·   Meetings

About

The Sugar Labs BugSquad keeps track of current bugs in the Sugar software and tries to make sure that bugs are triaged and handled correctly. The team does not do testing itself. This is done by the downstream projects shipping Sugar. See testing.

You need only be interested in the programming process to be in the BugSquad; in fact it is a great way to return something to the Sugar community if you cannot program. If you have an interest in the programming and development process, you can learn a great deal from the communications of those involved. However, see this thread for what can happen if insufficient respect and deference is applied: http://www.mail-archive.com/devel@lists.laptop.org/msg18897.html.

The squad is modeled on the GNOME BugSquad: https://webstats.gnome.org/Bugsquad/

How bugs are tracked

  • We use trac to keep track of bugs in the Sugar software. The Sugar Labs trac instance can be found at bugs.sugarlabs.org.
  • See BugSquad/Bug Report for an introduction to bug reporting.
  • Other Linux distributions where Sugar runs have their own upstream bug tracking systems.

Upstream bugs

When you find a bug in a package we do not directly maintain, please report it upstream

How to join the squad

As mentioned above, virtually anyone can be helpful. Best way to get started is by reading the BugSquad/Triage Guide and to join us at #sugar on irc.freenode.net.

Subpages