Fedora 13 Alpha Release Criteria

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(Add fedora-qa link)
m (Changed category)
 
(26 intermediate revisions by 5 users not shown)
Line 3: Line 3:
 
# Publicly release installable media versions of a [[Feature_Freeze_Policy|feature complete]] test release   
 
# Publicly release installable media versions of a [[Feature_Freeze_Policy|feature complete]] test release   
 
# Test [[Releases/13/FeatureList|accepted features of {{FedoraVersion|long|13}}]]
 
# Test [[Releases/13/FeatureList|accepted features of {{FedoraVersion|long|13}}]]
# Execute all Fedora 13 Alpha test plans <ref>https://fedorahosted.org/fedora-qa/ticket/35</ref>
 
 
# Identify as many [https://bugzilla.redhat.com/showdependencytree.cgi?id={{FedoraVersion|short|13}}beta&hide_resolved=1 {{FedoraVersion|short|13}}Beta blocker bugs] as possible
 
# Identify as many [https://bugzilla.redhat.com/showdependencytree.cgi?id={{FedoraVersion|short|13}}beta&hide_resolved=1 {{FedoraVersion|short|13}}Beta blocker bugs] as possible
 
# Identify as many [https://bugzilla.redhat.com/showdependencytree.cgi?id={{FedoraVersion|short|13}}blocker&hide_resolved=1 {{FedoraVersion|short|13}}Blocker blocker bugs] as possible
 
# Identify as many [https://bugzilla.redhat.com/showdependencytree.cgi?id={{FedoraVersion|short|13}}blocker&hide_resolved=1 {{FedoraVersion|short|13}}Blocker blocker bugs] as possible
Line 10: Line 9:
 
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.
 
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.
  
Release Requirements:
 
 
# All bugs blocking the [https://bugzilla.redhat.com/showdependencytree.cgi?id=f13alpha&hide_resolved=1 Alpha tracker] must be [[BugZappers/BugStatusWorkFlow#CLOSED|CLOSED]]
 
# All bugs blocking the [https://bugzilla.redhat.com/showdependencytree.cgi?id=f13alpha&hide_resolved=1 Alpha tracker] must be [[BugZappers/BugStatusWorkFlow#CLOSED|CLOSED]]
# All of the tests in the Fedora 13 Alpha Media Install test plan must be run (all failures are reviewed for consideration as [https://bugzilla.redhat.com/showdependencytree.cgi?id=f13alpha&hide_resolved=1 Fedora 13 Alpha Blocker bugs])
 
# All tests in the Fedora 13 Alpha Install Release test plan must be run
 
# All tests in the Fedora 13 Alpha Functional Release test plan must be run
 
# 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 installed system is able to download updates with yum
 
 
# 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
# Installer boots and runs on all [[Architectures#Primary_Architectures|primary architectures]]: i686 and x86_64
+
# The installer must boot (if appropriate) and run on all [[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 package source options
 +
# The installer must be able to use the DVD local package source options
 +
# The installer must be able to complete an installation using the text, graphical and VNC installation interfaces
 +
# The installer must be able to complete package installation with the default package set for each supported installation method
 +
# The installer must be able to complete an installation using IDE, SATA and SCSI storage devices, with the default file system and LVM
 +
# 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
 +
# The rescue mode of the installer must start successfully and be able to detect and mount an existing default installation
 +
# The installer must be able to report failures to Bugzilla, with appropriate information included
 +
# In most cases, the installed system must boot to a functional graphical environment (see [[Blocker_Bug_FAQ#Hardware_and_local_configuration_dependent_issues|Blocker_Bug_FAQ]])
 +
# 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 [https://admin.fedoraproject.org/accounts/ FAS]
 +
# The installed system must be able to download and install updates with yum and PackageKit
 +
 
 
<!--  
 
<!--  
 
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).
 
-->
 
-->
 
{{admon/note|Specificity|''Requirements'' are as specific as possible and stated affirmatively in the present tense}}
 
  
 
== Alpha Blocker Bugs ==
 
== Alpha Blocker Bugs ==
 
A bug is considered an Alpha blocker bug if '''any''' of the following criteria are met:
 
A bug is considered an Alpha 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) <!-- See http://en.wikipedia.org/wiki/Template:Date to make this point to the current rawhide critpath --> 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 (see definition of [[BugZappers/BugStatusWorkFlow#Priority_and_Severity|severity and priority]])
 
** Has a severity rating of ''high'' or greater and no reasonable workaround (see definition of [[BugZappers/BugStatusWorkFlow#Priority_and_Severity|severity and priority]])
Line 39: Line 42:
  
 
== Contingency Plan ==
 
== 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.   
+
* 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.
 
* 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]]
+
* This decision will be made at the [[Engineering_Readiness_Meetings |''Go/No-Go'' Meeting]].
  
 
== Confirming Alpha Requirements ==
 
== Confirming Alpha Requirements ==
Line 52: Line 55:
 
* [[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 18:09, 18 June 2010

Contents

[edit] 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. Identify as many F13Beta blocker bugs as possible
  4. Identify as many F13Blocker blocker bugs as possible

[edit] 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 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 package source options
  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 and LVM
  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 rescue mode of the installer must start successfully and be able to detect and mount an existing default installation
  11. The installer must be able to report failures to Bugzilla, with appropriate information included
  12. In most cases, the installed system must boot to a functional graphical environment (see Blocker_Bug_FAQ)
  13. 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
  14. The installed system must be able to download and install updates with yum and PackageKit


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


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

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

[edit] Related Pages