Fedora 13 Beta Release Criteria

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(Adjust <ref> link)
(add in specific installer requirements, revise to be more generic and refer to alpha criteria)
Line 10: Line 10:
  
 
Release Requirements:
 
Release Requirements:
 +
# All [[Fedora_13_Alpha_Release_Criteria|Fedora 13 Alpha release criteria]] must be met
 
# All bugs blocking the [https://bugzilla.redhat.com/showdependencytree.cgi?id=f13beta&hide_resolved=1 Beta tracker] must be [[BugZappers/BugStatusWorkFlow#CLOSED|CLOSED]]
 
# All bugs blocking the [https://bugzilla.redhat.com/showdependencytree.cgi?id=f13beta&hide_resolved=1 Beta tracker] must be [[BugZappers/BugStatusWorkFlow#CLOSED|CLOSED]]
# All of the tests in the Fedora 13 Beta Media Install test plan must be run (all failures are reviewed for consideration as [https://bugzilla.redhat.com/showdependencytree.cgi?id=f13beta&hide_resolved=1 Fedora 13 Beta Blocker bugs])
+
# The installer must boot (if appropriate) and run on all on [[Architectures#Primary_Architectures|primary architectures]] from default live image, DVD, multi-CD, and boot.iso install media
# All tests in the Fedora 13 Beta Install Release test plan must be run
+
# The installer must be able to use the HTTP, FTP and NFS remote installation source options
# All tests in the Fedora 13 Beta Functional Release test plan must be run
+
# The installer must be able to use the CD and DVD local installation source option
# In most cases, the installed system boots and starts up properly (see [[Blocker_Bug_FAQ#Hardware_and_local_configuration_dependent_issues|Blocker_Bug_FAQ]]).
+
# The installer must be able to use all kickstart delivery methods
# The installed system is able to download updates with yum.
+
# 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
# No file conflicts or unresolved package dependencies during a media-based (CD/DVD) install
+
# 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
# Installer boots and runs on all [[Architectures#Primary_Architectures|primary architectures]]: i686 and x86_64
+
# The rescue mode of the installer must start successfully and be able to detect and mount an existing default installation
 +
# The beta 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)
 
<!--  
 
<!--  
 
IF we need this ... we fail
 
IF we need this ... we fail
 
# The QA team has an installable testable Release Candidate for at least two full days (48 hours).
 
# The QA team has an installable testable Release Candidate for at least two full days (48 hours).
 
-->
 
-->
# All Alpha criteria have been met
 
# Installation
 
#* All boot media
 
#* Installation sources - http, ftp, nfs, CD, DVD
 
#* Display environments - text-mode, graphical, VNC
 
#* All kickstart delivery methods
 
#* Package set - Default
 
#* Partition - Default and encrypted default using entire disk or existing linux partition
 
#* Block devices - IDE, SATA, SCSI
 
#* RAID - ''Reasonable'' partitioning using software, hardware, and BIOS RAID.
 
#* Upgrade - preupgrade and media-based upgrade
 
#* Rescue mode starts properly and can detect/mount a default installation
 
# Virtualization - Beta release must install and boot on previous stable Fedora release using preferred virtualization technology.
 
# No file conflicts or unresolved package dependencies during a media-based (CD/DVD) install
 
  
 
{{admon/note|Specificity|Requirements are as specific as possible and stated affirmatively in the present tense}}
 
{{admon/note|Specificity|Requirements are as specific as possible and stated affirmatively in the present tense}}

Revision as of 20:20, 6 December 2009

Contents

Beta Objectives

The objectives of the Beta release are to:

  1. Publicly release installable media versions of a feature complete test release
  2. Finishing testing Fedora 13 Features
  3. Execute all Fedora 13 Beta test plans
  4. 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 intentional 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:

  1. All Fedora 13 Alpha release criteria must be met
  2. All bugs blocking the Beta tracker must be CLOSED
  3. 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
  4. The installer must be able to use the HTTP, FTP and NFS remote installation source options
  5. The installer must be able to use the CD and DVD local installation source option
  6. The installer must be able to use all kickstart delivery methods
  7. 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
  8. 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
  9. The rescue mode of the installer must start successfully and be able to detect and mount an existing default installation
  10. The beta 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)
Note.png
Specificity
Requirements are as specific as possible and stated affirmatively in the present tense

Beta Blocker Bugs

A bug is considered an Beta blocker bug if any of the following criteria are met:


Contingency Plan

  • If all of the Beta 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 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.

Related Pages