Fedora 13 Beta Release Criteria

Beta Objectives

The objectives of the Beta release are to:

1. Publicly release installable media versions of a feature complete test release
2. Finishing testing Fedora 13 Features
3. Execute all Fedora 13 Beta test plans
4. 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:

1. All bugs blocking the Beta tracker must be CLOSED
2. All of the tests in the Fedora 13 Beta Media Install test plan must be run (all failures are reviewed for consideration as Fedora 13 Beta Blocker bugs)
3. All tests in the Fedora 13 Beta Install Release test plan must be run
4. All tests in the Fedora 13 Beta Functional Release test plan must be run
5. In most cases, the installed system boots and starts up properly (see Blocker_Bug_FAQ).
6. The installed system is able to download updates with yum.
7. No file conflicts or unresolved package dependencies during a media-based (CD/DVD) install
8. Installer boots and runs on all primary architectures: i686 and x86_64
9. All Alpha criteria have been met
10. Installation
    • All boot media
    • Installation sources - http, ftp, nfs, CD, DVD
    • Display environments - text-mode, graphical, VNC
    • All kickstart delivery methods
    • Package set - Default
    • Partition - Default and encrypted default using entire disk or existing linux partition
    • Block devices - IDE, SATA, SCSI
    • RAID - Reasonable partitioning using software, hardware, and BIOS RAID.
    • Upgrade - preupgrade and media-based upgrade
    • Rescue mode starts properly and can detect/mount a default installation
11. Virtualization - Beta release must install and boot on previous stable Fedora release using preferred virtualization technology.
12. No file conflicts or unresolved package dependencies during a media-based (CD/DVD) install

Specificity
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 (see definition of severity and priority)
• Bug hinders execution of required Beta test plans or dramatically reduces test coverage
• Bug relates to an unmet Beta Release Requirement

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.

Related Pages

• Fedora Release Criteria
• Fedora 13 Alpha Release Criteria
• Fedora 13 Final Release Criteria
• Blocker Bug FAQ