From Fedora Project Wiki
(Copy'n'paste from F13) |
(add the proposed 'graphical boot menu for installer' criterion, add a 'without user intervention' clause to the 'installed system must boot' criterion) |
||
| Line 11: | Line 11: | ||
# All bugs blocking the [https://bugzilla.redhat.com/showdependencytree.cgi?id=f14alpha&hide_resolved=1 Alpha tracker] must be [[BugZappers/BugStatusWorkFlow#CLOSED|CLOSED]] | # All bugs blocking the [https://bugzilla.redhat.com/showdependencytree.cgi?id=f14alpha&hide_resolved=1 Alpha tracker] must be [[BugZappers/BugStatusWorkFlow#CLOSED|CLOSED]] | ||
# No file conflicts or unresolved package dependencies during a media-based (CD/DVD) install | # No file conflicts or unresolved package dependencies during a media-based (CD/DVD) install | ||
# All dedicated installer images must boot to the graphical boot menu and allow the user to select install options. If no option is selected, the installer should load after a reasonable timeout | |||
# The installer must boot (if appropriate) and run on all [[Architectures#Primary_Architectures|primary architectures]] from default live image, DVD, and boot.iso install media | # The installer must boot (if appropriate) and run on all [[Architectures#Primary_Architectures|primary architectures]] from default live image, DVD, and boot.iso install media | ||
# The installer must be able to use at least one of the HTTP or FTP remote package source options | # The installer must be able to use at least one of the HTTP or FTP remote package source options | ||
| Line 20: | Line 21: | ||
# 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 installer must be able to report failures to Bugzilla, with appropriate information included | # The installer must be able to report failures to Bugzilla, with appropriate information included | ||
# In most cases, the installed system must boot to a functional graphical environment (see [[Blocker_Bug_FAQ#Hardware_and_local_configuration_dependent_issues|Blocker_Bug_FAQ]]) | # In most cases, the installed system must boot to a functional graphical environment without user intervention (see [[Blocker_Bug_FAQ#Hardware_and_local_configuration_dependent_issues|Blocker_Bug_FAQ]]) | ||
# It must be possible to run the default web browser and a terminal application from the default desktop environment. The web browser must be able to download files, load extensions, and log into [https://admin.fedoraproject.org/accounts/ FAS] | # It must be possible to run the default web browser and a terminal application from the default desktop environment. The web browser must be able to download files, load extensions, and log into [https://admin.fedoraproject.org/accounts/ FAS] | ||
# The installed system must be able to download and install updates with yum and PackageKit | # The installed system must be able to download and install updates with yum and PackageKit | ||
Revision as of 19:03, 23 July 2010
Alpha Objectives
The objectives of the Alpha release are to:
- Publicly release installable media versions of a feature complete test release
- Test accepted features of Fedora 14
- Identify as many F14Beta blocker bugs as possible
- Identify as many F14Blocker 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 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.
- All bugs blocking the Alpha tracker must be CLOSED
- No file conflicts or unresolved package dependencies during a media-based (CD/DVD) install
- All dedicated installer images must boot to the graphical boot menu and allow the user to select install options. If no option is selected, the installer should load after a reasonable timeout
- The installer must boot (if appropriate) and run on all primary architectures from default live image, DVD, and boot.iso install media
- The installer must be able to use at least one of the HTTP or FTP remote package source options
- The installer must be able to use the DVD local package source options
- The installer must be able to complete an installation using the text, graphical and VNC installation interfaces
- The installer must be able to complete package installation with the default package set for each supported installation method
- The installer must be able to complete an installation using IDE, SATA and SCSI storage devices, with the default file system and LVM
- The installer must be able to complete an installation using the entire disk, existing free space, or existing Linux partitions methods, with or without encryption enabled
- The rescue mode of the installer must start successfully and be able to detect and mount an existing default installation
- The installer must be able to report failures to Bugzilla, with appropriate information included
- In most cases, the installed system must boot to a functional graphical environment without user intervention (see Blocker_Bug_FAQ)
- It must be possible to run the default web browser and a terminal application from the default desktop environment. The web browser must be able to download files, load extensions, and log into FAS
- The installed system must be able to download and install updates with yum and PackageKit
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 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 Alpha test plans or dramatically reduces test coverage
- Bug relates to an unmet Alpha Release Requirement
Contingency Plan
- If all of the Alpha Release Requirements are not met by 20:00 ETC on Wednesday (1:00 AM UTC Thursday) the 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.
- This decision will be made at the Go/No-Go Meeting.
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.