From Fedora Project Wiki
m (Adjust admon) |
|||
| Line 26: | Line 26: | ||
# The QA team has an installable testable Release Candidate for at least two full days (48 hours). | # The QA team has an installable testable Release Candidate for at least two full days (48 hours). | ||
--> | --> | ||
{{admon/note| | {{admon/note|Specificity|Requirements are as specific as possible and stated affirmatively in the present tense}} | ||
== Beta Blocker Bugs == | == Beta Blocker Bugs == | ||
Revision as of 17:45, 6 December 2009
This page is a draft only
It is still under construction and content may change. Do not rely on the information on this page. This page is a proposal for Fedora 13. It has not been accepted or officially reviewed and should not be relied on.
It is still under construction and content may change. Do not rely on the information on this page. This page is a proposal for Fedora 13. It has not been accepted or officially reviewed and should not be relied on.
Eventually this page will become a template which can be copy/pasted as a new page for each release.
Beta Objectives
The objectives of the Beta release are to:
- Publicly release installable media versions of a feature complete test release
- Finishing testing Fedora 13 Features
- Execute all Fedora 13 Beta test plans
- Identify as many F13Blocker bugs as possible
Beta Release Requirements
In order to be the released to the general public, the Beta Candidate (RC) must meet all of the following criteria. This is intentional to make the decision process as clear and straightforward as possible. Mostly met items are incomplete until they are met. Optional and nice to have items should not be included in this list.
Release Requirements:
- All bugs blocking the Beta tracker must be CLOSED
- All of the tests in the Fedora 13 Beta Media Install test plan must be 100% executed (all failures are reviewed for consideration as Fedora 13 Beta Blocker bugs)
- All tests in the Fedora 13 Beta Install Release test plan must be 100% executed
- All tests in the Fedora 13 Beta Functional Release test plan must be 100% executed
- In most cases, the installed system boots and starts up properly (see Blocker_Bug_FAQ).
- The installed system is able to download updates with yum.
- No file conflicts or unresolved package dependencies during a media-based (CD/DVD) install
- Installer boots and runs on all primary architectures: i686 and x86_64
Specificity
Requirements are as specific as possible and stated affirmatively in the present tense
Requirements are as specific as possible and stated affirmatively in the present tense
Beta Blocker Bugs
A bug is considered an Beta blocker bug if any of the following criteria are met:
- A bug in a Critical Path (see http://kojipkgs.fedoraproject.org/mash/rawhide-20091201/logs/critpath.txt) package that:
- Cannot be fixed with a future rawhide update
- Has a severity rating of high or greater and no reasonable workaround
- Bug hinders execution of required Beta testplans or dramatically reduces test coverage
- Bug relates to an unmet Beta Release Requirement (see above)
Blocker Bug details are less specific and provide general guidance about what bugs are considered blocker bugs. Specific requirements that must be present to release should be explicitly stated in the Release Requirements section
Contingency Plan
- If all of the Beta Release Requirements are not met by 20:00 UTC on the Wednesday one week prior to release day, the release will be delayed by one week so that the Beta Release Requirements can be met. One week will be added to all remaining tasks in the release schedule, including the final release date.
- * This decision will be made at the Go/No-Go Meeting
Confirming Beta Requirements
QA has the responsibility of determining whether the criteria for the release has been met (as outlined above) through discussion with Development and Release Engineering. QA's findings will be reviewed and discussed at the Go/No-Go meeting.