Fedora 13 Final Release Criteria

From FedoraProject

Revision as of 17:58, 25 November 2009 by Jlaska (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 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. No unfixed bugs blocking the F13Blocker tracker
    • No bugs in NEW or ASSIGNED
    • All MODIFIED bugs have been verified
  2. All of the tests in the Fedora 13 Final Media Install test plan must be 100% executed
  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. The installed system boots and starts up properly
  6. The installed system is able to download updates with yum.
  7. No file conflicts during install
  8. Installer boots and runs on all primary architectures: i686 and x86_64
  9. The QA team has an installable testable Release Candidate for at least three full days (72 hours).
  10. All services in a default install start properly
  11. No SELinux 'AVC: denied' messages on initial boot and subsequent login
  12. No regressions in functionality in critical path packages from the previous major release
  13. Rescue mode starts properly and can detect/mount a default installation
  14. Rescue mode starts properly and can detect/mount LVM, encrypted, dmraid and mdraid installations
  15. The files /root/install.log and /var/log/anaconda.log are free of error messages.
  16. No unfixed or undocumented data corruptor bugs.
  17. The installed system runs normally if the user chooses to install without SELinux.
  18. Menu sanity - the following criteria refer to both a live image and default installed system.
    1. All Applications menu items 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 click-through test, e.g. have working Help and Help -> About menu items.
    4. There is no Other menu
    5. No application appears twice in the menus--in particular, things under System do not appear under Applications.
  19. Panel: All elements of the default panel configuration are 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 <<NEED LINK>> package that:
    • Cannot be fixed with a future rawhide update
    • Is part of the media kit
    • 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 Tuesday at 20:00 UTC (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.

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