(add link to test-announce list) |
(trim tools and procedures a bit (merge finding duplicates into finding bugs, as the one has a link to the other)) |
||
| Line 24: | Line 24: | ||
* [[BugsAndFeatureRequests|Bugzilla Primer]] | * [[BugsAndFeatureRequests|Bugzilla Primer]] | ||
* [[BugZappers/Components and Triagers|Components and Triagers]] - Tracking progress and who's working on what | * [[BugZappers/Components and Triagers|Components and Triagers]] - Tracking progress and who's working on what | ||
* [[BugZappers/FindingBugs|Finding Bugs]] help | * [[BugZappers/FindingBugs|Finding Bugs]] help (including finding duplicate bugs) | ||
* [[BugZappers/How to Triage|How to Triage]] - Includes checklists for use when triaging bugs | * [[BugZappers/How to Triage|How to Triage]] - Includes checklists for use when triaging bugs | ||
* [[BugZappers/HouseKeeping|Housekeeping]] processes tied to the Fedora release cycle | * [[BugZappers/HouseKeeping|Housekeeping]] processes tied to the Fedora release cycle | ||
Revision as of 20:38, 1 October 2009
Who Are The BugZappers?
We are a group of volunteers and Red Hat employees whose primary mission is to review and triage bug report submissions on bugzilla.redhat.com, acting as a bridge between users and developers to aid in fixing and closing bugs.
The Bugs/Common content is one useful page we help maintain.
Help Wanted
Triaging bugs helps package maintainers spend more time on actually fixing bugs, and provides needed assistance to other Fedora users. No programming knowledge is necessary, and triagers don't necessarily need to understand the bugs they are working on - just help others communicate about them. To find out more about why and how to become a BugZapper, see Joining.
Responsibilities
- Triage Fedora bugs in Bugzilla. Request missing information, verify correct component has been chosen, and close duplicates.
- Nominate "target" and "blocker" bugs (tracked here) that should be fixed before the next release, according to the release criteria.
- Perform housekeeping during release EOL ("End of Life") transitions in coordination with ReleaseEngineering.
Tools and Procedures
- The BugZappers/Tools page contains several tools and scripts that are of use to BugZappers, including Greasemonkey scripts to make triaging quicker and easier.
- Bugzilla Primer
- Components and Triagers - Tracking progress and who's working on what
- Finding Bugs help (including finding duplicate bugs)
- How to Triage - Includes checklists for use when triaging bugs
- Housekeeping processes tied to the Fedora release cycle
- Stock Responses
- Bug Lifecycle
Communication
BugZappers meetings are held on Tuesdays at 1500 UTC (10 AM EDT) in #fedora-meeting on freenode. Everyone is welcome, and we invite you to come and participate. Topics of discussion for the next meeting as well as IRC transcripts of previous meetings can be found here BugZappers Meetings.
Triage Days are held each week immediately following the meeting in #fedora-bugzappers, for experienced Bugzappers to triage together and help new Bugzappers get started.
You can also find us on #fedora-bugzappers, stop by and say hello and feel free to ask any questions you have. Also, you can keep up to date with what is going on in the BugZappers by subscribing to the fedora-test-list@redhat.com mailing list. Alternatively, the test-announce list carries only important event announcements, if you do not want the traffic of the full list.