|
|
| (5 intermediate revisions by the same user not shown) |
| Line 1: |
Line 1: |
| == Background ==
| |
|
| |
|
| Fedora uses a system of ''tracker bugs'' to keep track of ''release blocker bugs'' - bugs that are blocking its milestone releases (Alpha, Beta, Final) and which must be fixed before these releases can proceed. The [[Fedora_Release_Criteria]] should be used to determine whether a bug is a blocker for a given release. This page defines the process by which bugs are proposed, reviewed and accepted as blocker bugs, and how blocker bugs are then tracked.
| |
|
| |
| See also the [[QA:SOP_freeze_exception_bug_process|freeze exception bug process]], which defines the similar process for freeze exception bugs - those which do not block the release, but which are considered high priority for tracking and fixing and for which fixes will be accepted even during release freezes.
| |
| {{Blocker_freeze_exception_schedule|type=blocker}}
| |
| {{Blocker_freeze_exception_proposing|type=blocker|typecamel=Blocker}}
| |
| {{Blocker_freeze_exception_reviewing|type=blocker|typecamel=Blocker}}
| |
| === Normal, 0-Day and Previous Release blockers ===
| |
|
| |
| The whiteboard fields {{code|AcceptedBlocker}}, {{code|Accepted0Day}} and {{code|AcceptedPreviousRelease}} are used to distinguish between three categories of blocker bug. {{code|AcceptedBlocker}} is the most common case. This is used for bugs where the fix must appear as part of the final frozen release itself (usually, on one of the media). {{code|Accepted0Day}} is used for cases where the fix does not need to appear in the final frozen release, but must be available as an update on release day. {{code|AcceptedPreviousRelease}} is used for cases where the fix must appear as an update for one or more stable releases.
| |
|
| |
| The most common case for both {{code|Accepted0Day}} and {{code|AcceptedPreviousRelease}} is upgrade-related problems. For instance, there may be a bug in the upgrade mechanism itself; this will usually need to be fixed in the existing stable releases, not the new release. There may be a bug in a package in the new release which prevents systems with that package installed upgrading correctly; the fix for such a bug does not need to be part of the frozen final release, as upgrades typically use the online package repositories, but if the affected package is very commonly installed, we may decide that we wish to ensure the fixed package is available from the updates repository on release day, and make the bug an accepted 0-Day blocker.
| |
| {{Blocker_freeze_exception_automatic|type=blocker|typecamel=Blocker|blocking=release-blocking}}
| |
| {{Blocker_freeze_exception_tracking|type=blocker}}
| |
|
| |
| == See also ==
| |
| * [[Blocker Bug FAQ]]
| |
