Difference between revisions of "BugSquad"
m (move testing sub heading to bugsquad/testing) |
m (add links to child pages) |
||
Line 9: | Line 9: | ||
== Testing Sugar == | == Testing Sugar == | ||
− | + | see [[BugSquad/Testing]]] | |
== Working with Distributions == | == Working with Distributions == | ||
Good Communication with downstream distributions is essential for receiving bug reports and patches from outside developers. | Good Communication with downstream distributions is essential for receiving bug reports and patches from outside developers. | ||
− | + | see [[BugSquad/Downstream]] | |
− | |||
− | |||
− | |||
== Working with Application Developers == | == Working with Application Developers == | ||
== Triaging Bug Reports == | == Triaging Bug Reports == | ||
+ | see [[BugSquad/Triage]] | ||
== Managing the Bug Database == | == Managing the Bug Database == |
Revision as of 18:27, 26 May 2008
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.
editors note: Currently, this page is an outline for developing an outline of the BugSquad's responsibility. Gradually, the outline will become the bugsquad wiki page hierarchy.
What We Do
Testing Sugar
see BugSquad/Testing]
Working with Distributions
Good Communication with downstream distributions is essential for receiving bug reports and patches from outside developers.
Working with Application Developers
Triaging Bug Reports
see BugSquad/Triage
Managing the Bug Database
Quicklinks
Open Tickets
Here is a link to the current open tickets for Sugar [1].
New Tickets
Here is a link to the page for opening a new ticket [2] (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.