Fedora 15 Beta Release Criteria

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(make changes discussed in thread http://lists.fedoraproject.org/pipermail/test/2011-March/097859.html)
(revise the upgrade criterion as discussed in thread http://lists.fedoraproject.org/pipermail/test/2011-March/098288.html)
 
Line 20: Line 20:
 
# The installer must be able to use all kickstart delivery methods
 
# The installer must be able to use all kickstart delivery methods
 
# The installer must be able to create and install to software, hardware or BIOS RAID-0, RAID-1 or RAID-5 partitions for anything except /boot
 
# The installer must be able to create and install to software, hardware or BIOS RAID-0, RAID-1 or RAID-5 partitions for anything except /boot
# The installer must be able to successfully complete an upgrade installation from a clean, fully updated default installation of the previous stable Fedora release, either via preupgrade or by booting to the installer manually
+
# The installer must be able to successfully complete an upgrade installation from a clean, fully updated default installation (from any official install medium) of the previous stable Fedora release, either via preupgrade or by booting to the installer manually. The upgraded system must meet all release criteria
 
# Any installation method or process designed to run unattended must do so (there should be no prompts requiring user intervention)
 
# Any installation method or process designed to run unattended must do so (there should be no prompts requiring user intervention)
 
# The rescue mode of the installer must be able to detect and mount (read-write and read-only) LVM, encrypted, and RAID (BIOS, hardware, and software) installations
 
# The rescue mode of the installer must be able to detect and mount (read-write and read-only) LVM, encrypted, and RAID (BIOS, hardware, and software) installations

Latest revision as of 19:27, 29 March 2011

Contents

[edit] Beta Objectives

The objectives of the Beta release are to:

  1. Publicly release installable media versions of a code complete test release: Beta is the last widely co-ordinated test release point in any given release cycle
  2. Finish testing Fedora 15 Features
  3. Identify as many F15Blocker bugs as possible

[edit] 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 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.

There may be times where a requirement is unmet only in a particular configuration, such as with some keyboard layouts but not others, or if a particular character is used in a username, password or passphrase. In such cases, the release team should use their judgment and refer to precedent to determine whether or not the issue should be considered to block the release. They should consider the number of users likely to be affected by the issue, the severity of the case when the issue is encountered, and the ease or otherwise with which the issue can be avoided by both informed and uninformed users.

Release Requirements:

  1. All Fedora 15 Alpha Release Criteria must be met
  2. All bugs blocking the Beta tracker must be CLOSED
  3. The installer must boot (if appropriate) and run on all primary architectures from default live image, DVD, multi-CD, and boot.iso install media
  4. The installer must boot and run on systems using EFI other than Apple Macs
  5. The installer must be able to use the HTTP, FTP and NFS remote package source options
  6. The installer must be able to use the CD and DVD local package source options
  7. At the package installation stage, the install should show no uncategorized package groups
  8. The installer must be able to use all kickstart delivery methods
  9. The installer must be able to create and install to software, hardware or BIOS RAID-0, RAID-1 or RAID-5 partitions for anything except /boot
  10. The installer must be able to successfully complete an upgrade installation from a clean, fully updated default installation (from any official install medium) of the previous stable Fedora release, either via preupgrade or by booting to the installer manually. The upgraded system must meet all release criteria
  11. Any installation method or process designed to run unattended must do so (there should be no prompts requiring user intervention)
  12. The rescue mode of the installer must be able to detect and mount (read-write and read-only) LVM, encrypted, and RAID (BIOS, hardware, and software) installations
  13. When booting a system installed without a graphical environment, or when using a correct configuration setting to cause an installed system to boot in non-graphical mode, the system should provide a working login prompt without any unintended user intervention when boot is complete, and all virtual consoles intended to provide a working login prompt should do so
  14. The release must boot successfully as a virtual guest in a situation where the virtual host is running the same release (using Fedora's current preferred virtualization technology)
  15. The release must boot successfully as a virtual guest in a situation where the virtual host is running the previous stable Fedora release (using Fedora's current preferred virtualization technology)
  16. The release must boot successfully as a virtual guest in a situation where the virtual host is running a supported Xen implementation
  17. In most cases, the installed system must be able to play back sound with gstreamer-based applications (see Blocker_Bug_FAQ)
  18. No part of the default desktop's panel (or equivalent) configuration should crash or be entirely non-functional on boot of the installed system using default installation choices
  19. Automatic mounting on insertion of removable media must work in the default desktop environment
  20. The desktop default update manager must not periodically check for updates when the system is booted live, but must periodically check for updates when running on an installed system
  21. The desktop's offered mechanisms (if any) for shutting down, logging out and rebooting must work

[edit] 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 package that:
    • Cannot be fixed with a future rawhide update
    • Has a severity rating of high or greater and no reasonable workaround (see definition of severity and priority)
  • Bug hinders execution of required Beta test plans or dramatically reduces test coverage
  • Bug relates to an unmet Beta Release Requirement

[edit] Contingency Plan

  • If all of the Beta Release Requirements are not met by 20:00 UTC on Wednesday the 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.
  • This decision will be made at the Go/No-Go Meeting.

[edit] 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.

[edit] Related Pages