Fedora 13 Beta Release Criteria

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(Beta Objectives)
(Undo revision 183041 by Adamwill (Talk) - meant to edit 14, not 13)
 
(39 intermediate revisions by 6 users not shown)
Line 1: Line 1:
{{draft | This page is a proposal for Fedora 13.  It has not been accepted or officially reviewed and should not be relied on.}}
 
 
{{admon/tip|Eventually this page will become a template which can be copy/pasted as a new page for each release.}}
 
 
 
== Beta Objectives ==
 
== Beta Objectives ==
 
The objectives of the Beta release are to:
 
The objectives of the Beta release are to:
# Publicly release installable media versions of a [[Feature_Freeze_Policy|feature complete]] test release   
+
# Publicly release installable media versions of a [[Feature_Freeze_Policy|code complete]] test release: Beta is the last widely co-ordinated test release point in any given release cycle  
# Finishing testing [[Releases/13/FeatureList| Fedora 13 Features]]
+
# Finish testing [[Releases/13/FeatureList| Fedora 13 Features]]
# Execute all Fedora 13 Beta test cases
+
 
# Identify as many [https://bugzilla.redhat.com/showdependencytree.cgi?id=f13blocker&hide_resolved=1| F13Blocker] bugs as possible
 
# Identify as many [https://bugzilla.redhat.com/showdependencytree.cgi?id=f13blocker&hide_resolved=1| F13Blocker] bugs as possible
  
 
== Beta Release Requirements ==
 
== 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.
+
In order to be the released to the general public, the Beta 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.
  
 
Release Requirements:
 
Release Requirements:
# No open bugs blocking the [https://bugzilla.redhat.com/showdependencytree.cgi?id=f13beta&hide_resolved=1 Beta tracker]
+
# All [[Fedora_13_Alpha_Release_Criteria|Fedora 13 Alpha release criteria]] must be met
# All of the tests in the Fedora 13 Beta Media Install test plan must be 100% executed
+
# All bugs blocking the [https://bugzilla.redhat.com/showdependencytree.cgi?id=f13beta&hide_resolved=1 Beta tracker] must be [[BugZappers/BugStatusWorkFlow#CLOSED|CLOSED]]
# All tests in the Fedora 13 Beta Install Release test plan must be 100% executed
+
# The installer must boot (if appropriate) and run on all [[Architectures#Primary_Architectures|primary architectures]] from default live image, DVD, multi-CD, and boot.iso install media
# All tests in the Fedora 13 Beta Functional Release test plan must be 100% executed
+
# The installer must boot and run on systems using EFI other than Apple Macs
# The installed system boots and starts up properly
+
# The installer must be able to use the HTTP, FTP and NFS remote package source options
# The installed system is able to download updates with yum.
+
# The installer must be able to use the CD and DVD local package source options
# No file conflicts during install
+
# At the package installation stage, the install should show no uncategorized package groups
# Installer boots and runs on all [[Architectures#Primary_Architectures|primary architectures]]: i686 and x86_64
+
# The installer must be able to use all kickstart delivery methods
 +
# 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
 +
# 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
 +
# The rescue mode of the installer must be able to detect and mount (read-write and read-only) LVM, encrypted, and RAID (BIOS, hardware, and software) installations
 +
# The release must boot successfully as a virtual guest in a situation where the virtual host is running the same release (using Fedora's current preferred virtualization technology)
 +
# The 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)
 +
# The release must boot successfully as a virtual guest in a situation where the virtual host is running a supported Xen implementation
 +
# In most cases, the installed system must be able to play back sound with gstreamer-based applications (see [[Blocker_Bug_FAQ#Hardware_and_local_configuration_dependent_issues|Blocker_Bug_FAQ]])
 +
# No part of the default desktop's panel (or equivalent) configuration should crash on boot of the installed system using default installation choices
 +
# Automatic mounting on insertion of removable media must work in the default desktop environment
 +
<!--
 +
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).
 
+
-->
{{admon/note|''Requirements'' are as specific as possible and stated affirmatively in the present tense}}
+
  
 
== Beta Blocker Bugs ==
 
== Beta Blocker Bugs ==
 
A bug is considered an Beta blocker bug if '''any''' of the following criteria are met:
 
A bug is considered an Beta blocker bug if '''any''' of the following criteria are met:
* A bug in a ''Critical Path'' (see http://kojipkgs.fedoraproject.org/mash/rawhide-20091201/logs/critpath.txt) package that:  
+
* A bug in a [[Critical Path Packages|Critical Path package]] that:
 
** Cannot be fixed with a future rawhide update
 
** Cannot be fixed with a future rawhide update
** Has a severity rating of ''high'' or greater and no reasonable workaround  
+
** Has a severity rating of ''high'' or greater and no reasonable workaround (see definition of [[BugZappers/BugStatusWorkFlow#Priority_and_Severity|severity and priority]])
* Bug hinders execution of required Beta testplans or dramatically reduces test coverage
+
* Bug hinders execution of required Beta test plans or dramatically reduces test coverage
* Bug relates to an unmet Beta Release Requirement (see above)
+
* Bug relates to an unmet [[#Beta_Release_Requirements|Beta Release Requirement]]
 
+
<!--
{{admon/note|''Blocker Bug'' details are less specific and provide general guidance about what bugs are considered blocker bugs.  Specific requirements that ''must'' be present to release should be explicitly stated in the ''Release Requirements'' section}}
+
Specific requirements that ''must'' be present to release should be explicitly stated in the ''Release Requirements'' section  
 +
-->
  
 
== Contingency Plan ==
 
== 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.
+
* If all of the ''Beta Release Requirements'' are not met by 20:00 UTC on Wednesday the week prior to release day, the release will be delayed by one week so that the Beta Release Requirements can be met.  
* * This decision will be made at the [[Engineering_Readiness_Meetings |''Go/No-Go'' Meeting]]
+
* 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 [[Engineering_Readiness_Meetings |''Go/No-Go'' Meeting]].
  
 
== Confirming Beta Requirements ==
 
== 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.
+
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 [[Engineering_Readiness_Meetings |''Go/No-Go'' Meeting]].
  
 
== Related Pages ==
 
== Related Pages ==
Line 49: Line 56:
 
* [[Fedora_13_Final_Release_Criteria |Fedora 13 Final Release Criteria]]
 
* [[Fedora_13_Final_Release_Criteria |Fedora 13 Final Release Criteria]]
 
* [[Blocker_Bug_FAQ| Blocker Bug FAQ]]
 
* [[Blocker_Bug_FAQ| Blocker Bug FAQ]]
 +
 +
[[Category:Release Criteria]]

Latest revision as of 23:09, 28 June 2010

Contents

[edit] Beta Objectives

The objectives of the Beta release are to:

  1. Publicly release installable media versions of a code complete test release: Beta is the last widely co-ordinated test release point in any given release cycle
  2. Finish testing Fedora 13 Features
  3. Identify as many F13Blocker bugs as possible

[edit] 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 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.

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 primary architectures from default live image, DVD, multi-CD, and boot.iso install media
  4. The installer must boot and run on systems using EFI other than Apple Macs
  5. The installer must be able to use the HTTP, FTP and NFS remote package source options
  6. The installer must be able to use the CD and DVD local package source options
  7. At the package installation stage, the install should show no uncategorized package groups
  8. The installer must be able to use all kickstart delivery methods
  9. 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
  10. 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
  11. The rescue mode of the installer must be able to detect and mount (read-write and read-only) LVM, encrypted, and RAID (BIOS, hardware, and software) installations
  12. The release must boot successfully as a virtual guest in a situation where the virtual host is running the same release (using Fedora's current preferred virtualization technology)
  13. The 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)
  14. The release must boot successfully as a virtual guest in a situation where the virtual host is running a supported Xen implementation
  15. In most cases, the installed system must be able to play back sound with gstreamer-based applications (see Blocker_Bug_FAQ)
  16. No part of the default desktop's panel (or equivalent) configuration should crash on boot of the installed system using default installation choices
  17. Automatic mounting on insertion of removable media must work in the default desktop environment

[edit] Beta Blocker Bugs

A bug is considered an Beta 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 Beta test plans or dramatically reduces test coverage
  • Bug relates to an unmet Beta Release Requirement

[edit] Contingency Plan

  • If all of the Beta Release Requirements are not met by 20:00 UTC on Wednesday the 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.

[edit] 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.

[edit] Related Pages