Template:Release criteria definition

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(fix a hardcoded alpha)
({{{prerelease|PRE-RELEASE}}} Blocker Bugs: s/rawhide/stable for final :))
Line 3: Line 3:
 
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}}} 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 rawhide 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

Revision as of 17:50, 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 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.