Fedora 14 Alpha Release Criteria

From FedoraProject

Revision as of 18:21, 7 October 2010 by Adamwill (Talk | contribs)

Jump to: navigation, search

Contents

Alpha Objectives

The objectives of the Alpha release are to:

  1. Publicly release installable media versions of a feature complete test release
  2. Test accepted features of Fedora 14
  3. Identify as many F14Beta blocker bugs as possible
  4. 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.

  1. All bugs blocking the Alpha tracker must be CLOSED
  2. There must be no file conflicts (cases where the files in some packages conflict but the packages have explicit Conflicts: tags are acceptable) or unresolved package dependencies during a media-based (CD/DVD) install
  3. 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
  4. The installer must boot (if appropriate) and run on all primary architectures from default live image, DVD, and boot.iso install media
  5. The installer must be able to use at least one of the HTTP or FTP remote package source options
  6. The installer must be able to use the DVD local package source options
  7. The installer must be able to complete an installation using the text, graphical and VNC installation interfaces
  8. The installer must be able to complete package installation with the default package set for each supported installation method
  9. The installer must be able to complete an installation using IDE, SATA and SCSI storage devices, with the default file system and LVM
  10. 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
  11. The rescue mode of the installer must start successfully and be able to detect and mount an existing default installation
  12. The installer must be able to report failures to Bugzilla, with appropriate information included
  13. In most cases, the installed system must boot to a functional graphical environment without user intervention (see Blocker_Bug_FAQ). For the Sugar environment, this is defined as home, group and neighbourhood views working, basic collaboration working, and the log activity working
  14. 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
  15. The installed system must be able to download and install updates with yum and PackageKit
  16. The default Fedora artwork must either refer to the current Fedora release under development (Fedora 14), or reference an interim release milestone (e.g. Alpha or Beta). If a release version number is used, it must match the current Fedora release under development. This includes artwork used in the installer, firstboot, graphical boot, graphical login and desktop background.


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.

Related Pages