From Fedora Project Wiki
(templatify the 'definition of a blocker bug' section of release criteria pages) |
(fix a hardcoded alpha) |
||
| Line 5: | Line 5: | ||
** Cannot be fixed with a future rawhide update | ** Cannot be fixed with a future rawhide 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 | * Bug hinders execution of required {{{prerelease|PRE-RELEASE}}} test plans or dramatically reduces test coverage | ||
* Bug relates to an unmet [[#{{{prerelease|PRE-RELEASE}}}_Release_Requirements|{{{prerelease|PRE-RELEASE}}} Release Requirement]] | * Bug relates to an unmet [[#{{{prerelease|PRE-RELEASE}}}_Release_Requirements|{{{prerelease|PRE-RELEASE}}} Release Requirement]] | ||
Revision as of 18:58, 18 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 rawhide 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.