BugZappers/HouseKeeping/Trackers

= Release Tracking Bugs =

Policy

 * The QA:SOP_blocker_bug_process and QA:SOP_nth_bug_process pages describe the general processes for handling blocker and nice-to-have bugs
 * Criteria for considering a bug to be a blocker to be added to a release tracker are set in the release criteria page for each public release (Alpha, Beta, and Final)
 * Another helpful reference may be the Blocker Bug FAQ
 * Fedora creates a series of tracker bugs at the beginning of each new release cycle for two release cycles in advance
 * For example, at the release of Fedora 13, Fedora 15 Blocker and Accepted bugs were created. At the release of Fedora 14, Fedora 16 blocker and target bugs will be created, etc.

Process
Create the following tracking bugs:
 * 1) Alpha (must fix prior to Alpha release)
 * 2) Alpha-accepted (nice-to-have fixes for Alpha release)
 * 3) Beta (must fix prior to Beta release)
 * 4) Beta-accepted (nice-to-have fixes for Beta release)
 * 5) Blocker (must fix prior to GA)
 * 6) -accepted (nice-to-have fixes for GA)
 * 7) Record new tracker bugs in the section  Current Tracker Bugs above
 * 8) After the Alpha release, move any remaining open bugs on the Alpha-accepted tracker to the Beta-accepted tracker; after the Beta release, move any remaining open bugs on the Beta-accepted tracker to the GA -accepted tracker; after the Final release, set any remaining open bugs on the GA -accepted tracker to no longer block any of these tracker bugs
 * 9) Remove the listing of tracker bugs in the section  Current Tracker Bugs once the release is GA

Tracker bugs should be created with the following attributes:
 * 1) Alias corresponding to the blocker and release. For example
 * 2) * Fedora 22 Alpha would be: F22Alpha
 * 3) * Fedora 22 Alpha Accepted would be: F22Alpha-accepted
 * 4) * Fedora 23 GA Blocker would be: F23Blocker
 * 5) * Fedora 23 GA Accepted would be: F23-accepted
 * 6) Keyword


 * A bugzilla query reporting all tracker bugs is here: here