From Fedora Project Wiki

Revision as of 17:39, 6 December 2009 by Notting (talk | contribs) (Final Release Requirements)

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.
Eventually this page will become a template which can be copy/pasted as a new page for each release.

Final Objectives

The objectives of the Final release are to:

  1. A polished final release suitable for general public consumption--meeting the needs of our Target Audience
  2. Execute all Fedora 13 Final test cases
  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 bugs blocking the F13Blocker tracker must be CLOSED
  2. All of the tests in the Fedora 13 Final Media Install test plan must be 100% executed (all failures are reviewed for consideration as Fedora 13 Blocker bugs)
  3. All tests in the Fedora 13 Final Install Release test plan must be 100% executed
  4. All tests in the Fedora 13 Final Functional Release test plan must 100% executed
  5. In most cases, the installed system boots and starts up properly (see Blocker_Bug_FAQ).
  6. The installed system is able to download updates with yum.
  7. No file conflicts or unresolved package dependencies during a media-based (CD/DVD) install
  8. Installer boots and runs on all primary architectures: i686 and x86_64
  9. All services in a default install start properly
  10. No SELinux 'AVC: denied' messages on initial boot and subsequent login
  11. No regressions in functionality in critical path packages from the previous major release
  12. Rescue mode starts properly and can detect/mount a default installation
  13. Rescue mode starts properly and can detect/mount LVM, encrypted, dmraid and mdraid installations
  14. The files /root/install.log and /var/log/anaconda.log are free of error messages.
  15. All known bugs that can cause corruption of user data are fixed or documented at _____________.
  16. The installed system runs normally if the user chooses to install without SELinux.
  17. Menu sanity - the following criteria refer to both a live image and default installed system.
    1. All Applications listed in the desktop menues have icons, and look ok together (ie no wild theme mix and blurry scaled icons)
    2. All applications listed under the Applications menu start successfully
    3. All applications listed under the Applications menu withstand a basic functionality test and do not crash after a few minutes of normal use. They also have working Help and Help -> About menu items.
    4. There is no Other menu
    5. No application unintentionally appears twice in the menus--in particular, things under System do not appear under Applications.
  18. Panel: All elements of the default panel configuration are functional.
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 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)
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