From Fedora Project Wiki
Note
This is a draft for review of proposed changes to the BugZappers main wiki page. It is incomplete and not a valid source of information.
This is a draft for review of proposed changes to the BugZappers main wiki page. It is incomplete and not a valid source of information.
Who Are We?
Our primary mission is to review bug report submissions on bugzilla.redhat.com and take action as nessesary, acting as a bridge between users and developers to aid in fixing and closing bugs.
Responsibilities
- Analyze and filter bug report submissions for correct component, actionable information and duplication on bugzilla.redhat.com.
- Re-assign components, mark duplicates or request further information when necessary.
- Advance Bug Work Flow status to NEEDINFO, ASSIGNED or CLOSED when applicable.
- Assign bugs to tracker list according to the ReleaseCriteria.
- Preform HouseKeeping necessary during release EOL (End-of-Life) transitions.
- Communicate through relevant mailing lists and the Bugzilla comment system to keep the Fedora community informed of impending or current EOL transitions, version change, etc.
Getting Involved
- See Joining for detailed information on account signups and getting access
Communicate
BugZappers meetings are held on Tuesday's at 17:00 UTC (10 AM EDT). Everyone is welcome, and we invite you to come and participate. Topics of discussion for next meeting as well as irc transcripts of previous meetings can be found here.
You can also find us on #fedora-bugzappers and #fedorabot on freenode. Stop by and say hello and feel free to ask any questions you have.
Keep up to date by subscribing to fedora-test-list@redhat.com mailing list.
Learn More About Triage
| Fedora Common Bugs | ||
|---|---|---|
| Fedora 8 | Fedora 9 | Fedora 10 |