Fedora 13 Alpha Release Criteria

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(Alpha Release Requirements)
(Alpha Release Requirements)
Line 18: Line 18:
 
# Package installation step can be completed with the default package set for each supported installation method
 
# Package installation step can be completed with the default package set for each supported installation method
 
# Installation can be completed with IDE, SATA and SCSI storage devices
 
# Installation can be completed with IDE, SATA and SCSI storage devices
# Installation can be completed using entire disk, existing free space, or existing Linux partitions methods, with encryption enabled
+
# Installation can be completed using entire disk, existing free space, or existing Linux partitions methods, with or without encryption enabled
 
# Installation failures can be properly reported to Bugzilla from the installer, with appropriate information included
 
# Installation failures can be properly reported to Bugzilla from the installer, with appropriate information included
 
# In most cases, the 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 system must boot to a functional graphical environment (see [[Blocker_Bug_FAQ#Hardware_and_local_configuration_dependent_issues|Blocker_Bug_FAQ]])

Revision as of 19:36, 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 [1]
  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. The installed system is able to download updates with yum
  3. No file conflicts or unresolved package dependencies during a media-based (CD/DVD) install
  4. Installer boots (if appropriate) and runs on all on primary architectures from default live image, DVD, and boot.iso install media
  5. Installer can use at least one of the http or ftp remote installation source option
  6. Text mode, graphical and VNC installation interfaces are able to complete an installation
  7. Package installation step can be completed with the default package set for each supported installation method
  8. Installation can be completed with IDE, SATA and SCSI storage devices
  9. Installation can be completed using entire disk, existing free space, or existing Linux partitions methods, with or without encryption enabled
  10. Installation failures can be properly reported to Bugzilla from the installer, with appropriate information included
  11. In most cases, the system must boot to a functional graphical environment (see Blocker_Bug_FAQ)
  12. Both Firefox and a terminal application can be run from the default desktop environment


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:


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


Cite error: <ref> tags exist, but no <references/> tag was found