From Fedora Project Wiki
(add a xen criterion (jesse)) |
|||
| Line 18: | Line 18: | ||
# The installer must be able to successfully complete an upgrade installation from a clean, fully updated default installation of the previous stable Fedora release, either via preupgrade or by booting to the installer manually | # The installer must be able to successfully complete an upgrade installation from a clean, fully updated default installation of the previous stable Fedora release, either via preupgrade or by booting to the installer manually | ||
# The rescue mode of the installer must start successfully and be able to detect and mount an existing default installation | # The rescue mode of the installer must start successfully and be able to detect and mount an existing default installation | ||
# The | # The release must boot successfully as a virtual guest in a situation where the virtual host is running the previous stable Fedora release (using Fedora's current preferred virtualization technology) | ||
# The release must boot successfully as a virtual guest in a situation where the virtual host is running an supported Xen implementation | |||
<!-- | <!-- | ||
IF we need this ... we fail | IF we need this ... we fail | ||
Revision as of 21:22, 7 December 2009
Beta Objectives
The objectives of the Beta release are to:
- Publicly release installable media versions of a code complete test release: Beta is the last widely co-ordinated test release point in any given release cycle
- Finish testing Fedora 13 Features
- 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 intended 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 Fedora 13 Alpha release criteria must be met
- All bugs blocking the Beta tracker must be CLOSED
- The installer must boot (if appropriate) and run on all on primary architectures from default live image, DVD, multi-CD, and boot.iso install media
- The installer must be able to use the HTTP, FTP and NFS remote package source options
- The installer must be able to use the CD and DVD local package source options
- The installer must be able to use all kickstart delivery methods
- The installer must be able to create and install to software, hardware or BIOS RAID-0, RAID-1 or RAID-5 partitions for anything except /boot
- The installer must be able to successfully complete an upgrade installation from a clean, fully updated default installation of the previous stable Fedora release, either via preupgrade or by booting to the installer manually
- The rescue mode of the installer must start successfully and be able to detect and mount an existing default installation
- The release must boot successfully as a virtual guest in a situation where the virtual host is running the previous stable Fedora release (using Fedora's current preferred virtualization technology)
- The release must boot successfully as a virtual guest in a situation where the virtual host is running an supported Xen implementation
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 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 Wednesday the 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.