From Fedora Project Wiki

Revision as of 23:02, 18 November 2009 by Poelstra (talk | contribs) (Created page with '{{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 t...')
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

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.

Beta Objectives

The objectives of the Beta release are to:

  1. Publicly release installable media versions of a feature complete test release
  2. Finishing testing accepted features of the release
  3. Execute all Beta test cases
    • <<link>>
  4. Identify as many F13Blocker blocker bugs as possible

Beta Release Requirements

In order to be the released to the general public, the Beta 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 Beta tracker
    • No bugs in NEW or ASSIGNED
    • All MODIFIED bugs have been verified
  2. All of the tests in the Fedora 13 Beta Media Install test plan must be 100% executed
    • Link:
  3. All tests in the Fedora 13 Beta Install Release test plan must be 100% executed
    • Link:
  4. All tests in the Fedora 13 Beta Functional Release test plan must be 100% executed
    • Link:
  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 two full days (48 hours).
Requirements are as specific as possible and stated affirmatively in the present tense

Beta Blocker Bugs

A bug is considered an Beta 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 Beta testplans or dramatically reduces test coverage
  • Bug relates to an unmet Beta 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 Beta 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 Beta Release Requirements can be met. One week will be added to all remaining tasks in the release schedule, including the final release date.

Confirming Beta 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.

Additional Notes, Thoughts, and Questions

  • It would be valuable to work in some bullets that address meeting the needs of the target audience for this release
    • What are the needs of the target audience for the Beta release?
  • What are the distinguishing features of the Beta Release?
    • How is it different from Alpha and Final?
    • Can we call them out a high level even if the distinguishing differences are in the required test cases.
    • Requirements should be more stringent than Alpha, but less so than Final
  • What problem is the Beta trying to solve?
  • How will decide if the Beta Release is a success?
  • How good does the Beta need to be?
  • Do we put the Fedora distribution or project at risk if we don't meet this criterion?
  • Do we negatively affect users or others if we don't meet this criterion?
  • What is unique about Beta blocker bugs and how can we capture that above (or tighten down in Beta and Final release sections)?
  • Make sure all MUST and SHOULD items from [QA/ReleaseCriteria] are integrated into the test plans referenced in the requirements

Related Pages

Retrieved from "https://fedoraproject.org/w/index.php?title=Fedora_13_Beta_Release_Criteria&oldid=137417"