Difference between revisions of "BugSquad"
Jump to navigation
Jump to search
m (add content to edit place holder -triage) |
|||
| Line 4: | Line 4: | ||
== Testing Sugar == | == Testing Sugar == | ||
| + | |||
| + | ====Teaching Users How to File Good Bugreports==== | ||
| + | Users are often the best source of bug information. | ||
| + | |||
| + | ====Teaching Bug Reporters How to Follow Up on Bugreports==== | ||
| + | Many bugreports rot because of lack of follow up from reporters. | ||
| + | |||
| + | ====Creating Best Practices for Developer Testing==== | ||
| + | |||
| + | ====Coordinate with Release Managers to Developer Pre-release test strategies=== | ||
== Working with Downstream Distribution == | == Working with Downstream Distribution == | ||
Revision as of 12:13, 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.
What We Do
Testing Sugar
Teaching Users How to File Good Bugreports
Users are often the best source of bug information.
Teaching Bug Reporters How to Follow Up on Bugreports
Many bugreports rot because of lack of follow up from reporters.
Creating Best Practices for Developer Testing
=Coordinate with Release Managers to Developer Pre-release test strategies
Working with Downstream Distribution
Working with Upstream Application Developers
Triaging Bug Reports
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.