From Fedora Project Wiki

< BugZappers‎ | HouseKeeping

Revision as of 15:50, 19 October 2010 by Adamwill (talk | contribs) (update with NTH / blocker process stuff)

Release Tracking Bugs

Current Tracker Bugs

Fedora 14

Blocker Alias Bug Number
Fedora 14 Alpha F14Alpha 611990
Fedora 14 Beta F14Beta 611991
Fedora 14 Beta Accepted (NTH) F14Beta-accepted 634253
Fedora 14 Blocker F14Blocker 538277
Fedora 14 Accepted (NTH) F14-accepted 635218
Fedora 14 Target F14Target 538278

Fedora 15

Blocker Alias Bug Number
Fedora 15 Alpha F15Alpha
Fedora 15 Alpha Accepted (NTH) F15Alpha-accepted
Fedora 15 Beta F15Beta
Fedora 15 Beta Accepted (NTH) F15Beta-accepted
Fedora 15 Blocker F15Blocker 617261
Fedora 15 Accepted (NTH) F15-accepted


  • 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)
  • 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.


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
    • Fedora 22 Alpha would be: F22Alpha
    • Fedora 22 Alpha Accepted would be: F22Alpha-accepted
    • Fedora 23 GA Blocker would be: F23Blocker
    • Fedora 23 GA Accepted would be: F23-accepted
  2. Keyword Tracking
  • A bugzilla query reporting all tracker bugs is here: here
Tracker bugs--commonly referred to as blocker bugs--are meta-bugs used to monitor a group of bugs that must be resolved before a specific release milestone and are therefore considered to block the release.
Aliases provide the ability to refer to a particular bugzilla by a user-defined term rather than the bug number. Some people find it easier to remember aliases rather than bug numbers.

Past Tracker Bugs

Fedora 13

Blocker Alias Bug Number
Fedora 13 Alpha F13Alpha 538273
Fedora 13 Beta F13Beta 538274
Fedora 13 Blocker F13Blocker 507681
Fedora 13 Target F13Target 507684

Fedora 12

Blocker Alias Bug Number
Fedora 12 Alpha F12Alpha 507676
Fedora 12 Beta F12Beta 507678
Fedora 12 Blocker F12Blocker 473303
Fedora 12 Target F12Target 473302

Fedora 11

Blocker Alias Bug Number
Fedora 11 Alpha F11Alpha 476773
Fedora 11 Beta F11Beta 476774
Fedora 11 Preview F11Preview 476775
Fedora 11 Blocker F11Blocker 446452
Fedora 11 Target F11Target 446451
Fedora 11 Intel Modesetting F11IntelKMS 487202

Fedora 10

Blocker Alias Bug Number
Fedora 10 Alpha F10Alpha 446445
Fedora 10 Beta F10Beta 446447
Fedora 10 Preview F10Preview 446449
Fedora 10 Blocker F10Blocker 438943
Fedora 10 Target F10Target 438944
Fedora 10 Desktop Target F10DesktopTarget 465130
Fedora 10 Desktop Blocker F10DesktopBlocker 457945
Fedora 10 Kernel Blocker F10KernelBlocker 466414