Fedora 13 Final Release Criteria

From FedoraProject

Revision as of 21:01, 6 December 2009 by Adamwill (Talk | contribs)

Jump to: navigation, search
Warning (medium size).png
This page is a draft only
It is still under construction and content may change. Do not rely on the information on this page. This page is a proposal for Fedora 13. It has not been accepted or officially reviewed and should not be relied on.
Idea.png
Eventually this page will become a template which can be copy/pasted as a new page for each release.

Contents

Final Objectives

The objectives of the Final release are to:

  1. A polished final release suitable for meeting the needs of our Target Audience
  2. Execute all Fedora 13 Final test plans
  3. Close all F13Blocker blocker bugs

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.

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 complete an installation using the text, graphical, VNC, telnet and cmdline installation interfaces
  4. The installer must be able to use all supported local and remote package source options
  5. The installer must be able to complete an installation using IDE, SATA, SCSI and iSCSI storage devices
  6. 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
  7. 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
  8. The rescue mode of the installer must be able to detect and mount LVM, encrypted, and RAID (BIOS, hardware, and software) installations
  9. All services in a default install must start properly
  10. All known bugs that can cause corruption of user data must be fixed or documented at Common_F13_Bugs
  11. The installed system must run normally if the user chooses to install without SELinux
  12. Menu sanity - the following criteria refer to both a live image and default installed system
    1. All Applications listed in the desktop menus must have icons which have a consistent appearance and sufficiently high resolution to not appear blurry
    2. All applications listed under the Applications menu must start successfully
    3. 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
    4. There must be no Other menu
    5. No application may unintentionally appear twice in the menus. In particular, things under System must not appear under Applications
  13. All elements of the default panel configuration must be functional
Note.png
Specificity
Requirements are as specific as possible and stated affirmatively in the present tense.

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 (see critpath.txt) 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)
Note.png
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

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.
  • 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 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.

Related Pages