Fedora 13 Final Release Criteria

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(restore SELinux criterion)
m (Changed category)
 
(20 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.}}
 
 
 
== Final Objectives ==
 
== Final Objectives ==
The objectives of the Final release are to:
+
The objective of the Final release is to:
# A polished final release suitable for meeting the needs of our ''Target Audience''
+
# Provide a polished final release suitable for meeting the needs of our ''Target Audience''
# Execute all [https://fedorahosted.org/fedora-qa/ticket/35 Fedora 13 Final test plans]
+
# Close all [https://bugzilla.redhat.com/showdependencytree.cgi?id=f13blocker&hide_resolved=1| F13Blocker] blocker bugs
+
  
 
== Final Release Requirements ==
 
== Final Release Requirements ==
In order to be the released to the general public, the Final 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 Final 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:
 
# All [[Fedora_13_Beta_Release_Criteria|Fedora 13 Beta release criteria]] must be met
 
# All [[Fedora_13_Beta_Release_Criteria|Fedora 13 Beta release criteria]] must be met
 
# All bugs blocking the [https://bugzilla.redhat.com/showdependencytree.cgi?id=f13blocker&hide_resolved=1 F13Blocker tracker] must be [[BugZappers/BugStatusWorkFlow#CLOSED|CLOSED]]
 
# All bugs blocking the [https://bugzilla.redhat.com/showdependencytree.cgi?id=f13blocker&hide_resolved=1 F13Blocker tracker] must be [[BugZappers/BugStatusWorkFlow#CLOSED|CLOSED]]
# The installer must be able to complete an installation using the text, graphical, VNC, telnet and cmdline installation interfaces
 
 
# The installer must be able to use all supported local and remote package source options
 
# The installer must be able to use all supported local and remote package source options
 
# The installer must be able to complete an installation using IDE, SATA, SCSI and iSCSI storage devices
 
# The installer must be able to complete an installation using IDE, SATA, SCSI and iSCSI storage devices
# The installer must be able to create and install to any workable partition layout using any supported file system, LVM, software, hardware or BIOS RAID, or combination of the above
+
# The installer must be able to create and install to any workable partition layout using any file system offered in a default installer configuration, LVM, software, hardware or BIOS RAID, or combination of the above
# The installer must be able to install alongside an existing Windows installation and either install a bootloader which can boot into the Windows installation, or leave the Windows bootloader untouched and working
+
# The installer must be able to install into free space alongside an existing clean single-partition Windows installation and either install a bootloader which can boot into the Windows installation, or leave the Windows bootloader untouched and working
# The rescue mode of the installer must be able to detect and mount LVM, encrypted, and RAID (BIOS, hardware, and software) installations
+
 
# All services in a default install must start properly
 
# All services in a default install must start properly
# There must be no SELinux 'AVC: denied' messages on initial boot and subsequent login
+
# In most cases, there must be no SELinux 'AVC: denied' messages or abrt crash notifications on initial boot and subsequent login (see [[Blocker_Bug_FAQ#Hardware_and_local_configuration_dependent_issues|Blocker_Bug_FAQ]])
# All known bugs that can cause corruption of user data must be fixed or documented at [[Common_F13_Bugs]]
+
# All known bugs that can cause corruption of user data must be fixed or documented at [[Common_F13_bugs]]
 
# The installed system must run normally if the user chooses to install without SELinux
 
# The installed system must run normally if the user chooses to install without SELinux
 
# Menu sanity - the following criteria refer to both a live image and default installed system
 
# Menu sanity - the following criteria refer to both a live image and default installed system
#* All ''Applications'' listed in the desktop menus must have icons which have a consistent appearance and sufficiently high resolution to not appear blurry
+
#* All ''Applications'' listed in the desktop menus must have icons which have a consistent appearance and sufficiently high resolution to avoid appearing blurry
 
#* All applications listed under the ''Applications'' menu must start successfully
 
#* All applications listed under the ''Applications'' menu must start successfully
 
#* All applications listed under the ''Applications'' menu must withstand a basic functionality test and not crash after a few minutes of normal use.  They must also have working ''Help'' and ''Help -> About'' menu items
 
#* All applications listed under the ''Applications'' menu must withstand a basic functionality test and not crash after a few minutes of normal use.  They must also have working ''Help'' and ''Help -> About'' menu items
 
#* There must be no ''Other'' menu
 
#* There must be no ''Other'' menu
#* No application may unintentionally appear twice in the menus. In particular, things under ''System'' must not appear under ''Applications''
+
#* No application may unintentionally appear twice in the menus. In particular, items under ''System'' must not appear under ''Applications''
 
# All elements of the default panel configuration must be functional
 
# All elements of the default panel configuration must be functional
 
{{admon/note|Specificity|''Requirements'' are as specific as possible and stated affirmatively in the present tense.}}
 
  
 
== Final Blocker Bugs ==
 
== Final Blocker Bugs ==
A bug is considered a [https://bugzilla.redhat.com/showdependencytree.cgi?id=f13blocker&hide_resolved=1| Final Blocker Bug] if '''any''' of the following criteria are met:
+
A bug is considered a [https://bugzilla.redhat.com/showdependencytree.cgi?id=f13blocker&hide_resolved=1 Final Blocker Bug] if '''any''' of the following criteria are met:
* A bug in a ''Critical Path'' (see [http://kojipkgs.fedoraproject.org/mash/rawhide-{{CURRENTYEAR}}{{CURRENTMONTH}}{{CURRENTDAY2}}/logs/critpath.txt 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  
 
* Bug hinders execution of required Final testplans or dramatically reduces test coverage
 
* Bug hinders execution of required Final testplans or dramatically reduces test coverage
 
* Bug relates to an unmet Final Release Requirement (see above)
 
* Bug relates to an unmet Final Release Requirement (see above)
 
+
<!--
{{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 ''Final Release Requirements'' are not met by 20:00 UTC on the Tuesday one week prior to release day, the release will be delayed by one week so that the Final Release Requirements can be met.   
+
* If all of the ''Final Release Requirements'' are not met by 20:00 UTC on Tuesday the week prior to release day, the release will be delayed by one week so that the Final 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 Final Requirements ==
 
== Confirming Final Requirements ==
Line 59: Line 50:
 
* [[Fedora_13_Beta_Release_Criteria |Fedora 13 Beta Release Criteria]]
 
* [[Fedora_13_Beta_Release_Criteria |Fedora 13 Beta Release Criteria]]
 
* [[Blocker_Bug_FAQ| Blocker Bug FAQ]]
 
* [[Blocker_Bug_FAQ| Blocker Bug FAQ]]
 +
* [[Packaging:Guidelines]]
  
[[Category:QA]]
+
[[Category:Release Criteria]]

Latest revision as of 18:09, 18 June 2010

Contents

[edit] Final Objectives

The objective of the Final release is to:

  1. Provide a polished final release suitable for meeting the needs of our Target Audience

[edit] Final Release Requirements

In order to be the released to the general public, the Final 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 Beta release criteria must be met
  2. All bugs blocking the F13Blocker tracker must be CLOSED
  3. The installer must be able to use all supported local and remote package source options
  4. The installer must be able to complete an installation using IDE, SATA, SCSI and iSCSI storage devices
  5. The installer must be able to create and install to any workable partition layout using any file system offered in a default installer configuration, LVM, software, hardware or BIOS RAID, or combination of the above
  6. The installer must be able to install into free space alongside an existing clean single-partition Windows installation and either install a bootloader which can boot into the Windows installation, or leave the Windows bootloader untouched and working
  7. All services in a default install must start properly
  8. In most cases, there must be no SELinux 'AVC: denied' messages or abrt crash notifications on initial boot and subsequent login (see Blocker_Bug_FAQ)
  9. All known bugs that can cause corruption of user data must be fixed or documented at Common_F13_bugs
  10. The installed system must run normally if the user chooses to install without SELinux
  11. Menu sanity - the following criteria refer to both a live image and default installed system
    • All Applications listed in the desktop menus must have icons which have a consistent appearance and sufficiently high resolution to avoid appearing blurry
    • All applications listed under the Applications menu must start successfully
    • All applications listed under the Applications menu must withstand a basic functionality test and not crash after a few minutes of normal use. They must also have working Help and Help -> About menu items
    • There must be no Other menu
    • No application may unintentionally appear twice in the menus. In particular, items under System must not appear under Applications
  12. All elements of the default panel configuration must be functional

[edit] Final Blocker Bugs

A bug is considered a Final 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
  • Bug hinders execution of required Final testplans or dramatically reduces test coverage
  • Bug relates to an unmet Final Release Requirement (see above)

[edit] Contingency Plan

  • If all of the Final Release Requirements are not met by 20:00 UTC on Tuesday the week prior to release day, the release will be delayed by one week so that the Final 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 Final 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