Fedora 13 Alpha Release Criteria

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(call out default file system specifically)
(Alpha Release Requirements)
Line 13: Line 13:
 
# 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
 
# The installer must boot (if appropriate) and run on all on [[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 on [[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 installation source options
+
# 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 installation source option
 
# The installer must be able to use the DVD local installation source option
 
# The installer must be able to complete an installation using the text, graphical and VNC installation interfaces
 
# The installer must be able to complete an installation using the text, graphical and VNC installation interfaces

Revision as of 20:54, 6 December 2009

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 13
  3. Execute all Fedora 13 Alpha test plans
  4. Identify as many F13Beta blocker bugs as possible
  5. 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 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. No file conflicts or unresolved package dependencies during a media-based (CD/DVD) install
  3. The installer must boot (if appropriate) and run on all on primary architectures from default live image, DVD, and boot.iso install media
  4. The installer must be able to use at least one of the HTTP or FTP remote package source options
  5. The installer must be able to use the DVD local installation source option
  6. The installer must be able to complete an installation using the text, graphical and VNC installation interfaces
  7. The installer must be able to complete package installation with the default package set for each supported installation method
  8. The installer must be able to complete an installation using IDE, SATA and SCSI storage devices, with the default file system
  9. 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
  10. The installer must be able to report failures to Bugzilla, with appropriate information included
  11. In most cases, the installed system must boot to a functional graphical environment (see Blocker_Bug_FAQ)
  12. It must be possible to run the default web browser and a terminal application from the default desktop environment
  13. The installed system must be able to download updates with yum


Note.png
Specificity
Requirements are as specific as possible and stated affirmatively in the present tense

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 (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 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 UTC on the Wednesday 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.
  • 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