Fedora 13 Alpha Release Criteria
The objectives of the Alpha release are to:
- Publicly release installable media versions of a feature complete test release
- Test accepted features of Fedora 13
- Execute all Fedora 13 test cases
- Identify as many F13Beta blocker bugs as possible
- Identify as many F13Blocker blocker bugs as possible
Alpha Release Requirements
In order to be the released to the general public, the Alpha 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 unfixed bugs blocking the Alpha tracker
- No bugs in NEW or ASSIGNED
- All MODIFIED bugs have been verified
- All of the tests in the Fedora 13 Alpha Media Install test plan must be 100% executed
- All tests in the Fedora 13 Alpha Install Release test plan must be 100% executed
- All tests in the Fedora 13 Alpha 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).
Alpha Blocker Bugs
A bug is considered an Alpha 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 Alpha testplans or dramatically reduces test coverage
- Bug relates to an unmet Alpha Release Requirement (see above)
- If all of the Alpha Release Requirements are not met by Tuesday at 20:00 UTC (one week prior to release day) the release will be delayed by one week so that the Alpha Release Requirements can be met. One week will be added to all remaining tasks in the release schedule, including the final release date.
Confirming Alpha 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.