From Fedora Project Wiki
(→{{{prerelease|PRE-RELEASE}}} Blocker Bugs: s/rawhide/stable for final :)) |
m (Support for arch= parameter) |
||
| Line 1: | Line 1: | ||
== {{{prerelease|PRE-RELEASE}}} Blocker Bugs == | {{Anchor|{{{prerelease|PRE-RELEASE}}} Blocker Bugs}} | ||
== {{{prerelease|PRE-RELEASE}}} {{#if:{{{arch|}}}|{{{arch}}} |}}Blocker Bugs == | |||
A bug is considered a {{{prerelease|PRE-RELEASE}}} blocker bug if '''any''' of the following criteria are met: | A bug is considered a {{{prerelease|PRE-RELEASE}}} {{#if:{{{arch|}}}|{{{arch}}} |}}blocker bug if '''any''' of the following criteria are met: | ||
* A bug in a [[Critical Path Packages|Critical Path package]] that: | * A bug in a [[Critical Path Packages|Critical Path package]] that: | ||
** Cannot be fixed with a future stable update | ** Cannot be fixed with a future stable update | ||
** Has a severity rating of ''high'' or greater and no reasonable workaround (see definition of [[BugZappers/BugStatusWorkFlow#Priority_and_Severity|severity and priority]]) | ** Has a severity rating of ''high'' or greater and no reasonable workaround (see definition of [[BugZappers/BugStatusWorkFlow#Priority_and_Severity|severity and priority]]) | ||
* Bug hinders execution of required {{{prerelease|PRE-RELEASE}}} test plans or dramatically reduces test coverage | * Bug hinders execution of required {{{prerelease|PRE-RELEASE}}} test plans or dramatically reduces test coverage | ||
* Bug relates to an unmet [[#{{{prerelease|PRE-RELEASE}}} | * Bug relates to an unmet [[#{{{prerelease|PRE-RELEASE}}}_{{#if:{{{arch|}}}|{{{arch}}}_|}}Release_Requirements|{{{prerelease|PRE-RELEASE}}} {{#if:{{{arch|}}}|{{{arch}}} |}}Release Requirement]] | ||
A Fedora [[Features/Policy|feature]] being incomplete, in and of itself, does not constitute a blocker bug. The feature process is separate from this process. Features are required to meet certain [[Features/Policy/Milestones|standards]] at certain points of the release cycle, but this is part of the [[Features/Policy|feature process]] and managed, tracked and enforced separately from this process. However, if a proposed feature being incomplete ''causes'' any of the above criteria to be met, then the bug is a release blocker. | A Fedora [[Features/Policy|feature]] being incomplete, in and of itself, does not constitute a blocker bug. The feature process is separate from this process. Features are required to meet certain [[Features/Policy/Milestones|standards]] at certain points of the release cycle, but this is part of the [[Features/Policy|feature process]] and managed, tracked and enforced separately from this process. However, if a proposed feature being incomplete ''causes'' any of the above criteria to be met, then the bug is a release blocker. | ||
Revision as of 19:26, 21 July 2011
PRE-RELEASE Blocker Bugs
A bug is considered a PRE-RELEASE blocker bug if any of the following criteria are met:
- A bug in a Critical Path package that:
- Cannot be fixed with a future stable update
- Has a severity rating of high or greater and no reasonable workaround (see definition of severity and priority)
- Bug hinders execution of required PRE-RELEASE test plans or dramatically reduces test coverage
- Bug relates to an unmet PRE-RELEASE Release Requirement
A Fedora feature being incomplete, in and of itself, does not constitute a blocker bug. The feature process is separate from this process. Features are required to meet certain standards at certain points of the release cycle, but this is part of the feature process and managed, tracked and enforced separately from this process. However, if a proposed feature being incomplete causes any of the above criteria to be met, then the bug is a release blocker.