Fedora 13 Beta Release Criteria
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 cases
- 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.
- No open bugs blocking the Beta tracker
- All of the tests in the Fedora 13 Beta Media Install test plan must be 100% executed
- 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
- The installed system boots and starts up properly
- The installed system is able to download updates with yum.
- No file conflicts during install
- Installer boots and runs on all primary architectures: i686 and x86_64
- The QA team has an installable testable Release Candidate for at least two full days (48 hours).
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 <<NEED LINK>> package that:
- Cannot be fixed with a future rawhide update
- Is part of the media kit
- 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)
- If all of the Beta Release Requirements are not met by Wednesday at 20:00 UTC (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.