User:Kparal/Draft Alpha Criteria

From FedoraProject

< User:Kparal(Difference between revisions)
Jump to: navigation, search
(Alpha Release Requirements)
(Alpha Release Requirements)
 
Line 55: Line 55:
 
==== Installer must run ====
 
==== Installer must run ====
 
The installer must run when launched normally from the supported images.
 
The installer must run when launched normally from the supported images.
{{hidden|header=Launched normally?|content='Launched normally' means from the boot menu on a dedicated installer image, and from the desktop on a live image.|headerstyle=background:#ccccff}}
+
{{hidden|header=Launched normally?|content='Launched normally' means from the boot menu on a dedicated installer image, and from the desktop on a live image.|headerstyle=font-style:italic;color:gray|ta1=left}}
  
 
{{anchor|remote-package-sources}}
 
{{anchor|remote-package-sources}}
Line 68: Line 68:
 
==== Installation interfaces ====
 
==== Installation interfaces ====
 
When using the dedicated installer images, the installer must be able to complete an installation using the text, graphical and VNC installation interfaces.
 
When using the dedicated installer images, the installer must be able to complete an installation using the text, graphical and VNC installation interfaces.
{{hidden|header=Showstoppers|content=This criterion covers showstopper bugs in the installer for which there isn't any other specific criterion: obviously, it can't 'complete an installation' if there's a showstopper. However, it does not mean that any failed installation test at all constitutes a release blocking issue: an installer which works fine in most cases but crashes when you attach it to a Hitachi hard disk on a wet Thursday is still 'able to complete an installation'.|headerstyle=background:#ccccff}}
+
{{hidden|header=Showstoppers|content=This criterion covers showstopper bugs in the installer for which there isn't any other specific criterion: obviously, it can't 'complete an installation' if there's a showstopper. However, it does not mean that any failed installation test at all constitutes a release blocking issue: an installer which works fine in most cases but crashes when you attach it to a Hitachi hard disk on a wet Thursday is still 'able to complete an installation'.|headerstyle=font-style:italic;color:gray|ta1=left}}
  
 
{{anchor|package-sets}}
 
{{anchor|package-sets}}
 
==== Package sets ====
 
==== Package sets ====
 
When doing a graphical install using the dedicated installer images, the installer must be able to install each of the release blocking desktops, as well as the minimal package set.
 
When doing a graphical install using the dedicated installer images, the installer must be able to install each of the release blocking desktops, as well as the minimal package set.
{{hidden|header=Not all at once!|content=This means you must be able to do a GNOME install, then start over and do a KDE install, then start over and do a minimal install. Not necessarily that you should be able to do any combination of them all at once.|headerstyle=background:#ccccff}}
+
{{hidden|header=Not all at once!|content=This means you must be able to do a GNOME install, then start over and do a KDE install, then start over and do a minimal install. Not necessarily that you should be able to do any combination of them all at once.|headerstyle=font-style:italic;color:gray|ta1=left}}
{{hidden|header=References|content=Modification from 'default package set' proposed [https://lists.fedoraproject.org/pipermail/test/2012-September/109860.html 2012-09-06]. Idea to cover the release blocking desktops and minimal package set proposed [https://lists.fedoraproject.org/pipermail/test/2012-September/109862.html 2012-09-06]. Implemented 2012-09-26. Note that the 'default package set' was later restored to the installer, but this criterion was still considered to be an improvement, and kept.|headerstyle=background:#ccccff}}
+
{{hidden|header=References|content=Modification from 'default package set' proposed [https://lists.fedoraproject.org/pipermail/test/2012-September/109860.html 2012-09-06]. Idea to cover the release blocking desktops and minimal package set proposed [https://lists.fedoraproject.org/pipermail/test/2012-September/109862.html 2012-09-06]. Implemented 2012-09-26. Note that the 'default package set' was later restored to the installer, but this criterion was still considered to be an improvement, and kept.|headerstyle=font-style:italic;color:gray|ta1=left}}
  
 
{{anchor|disk-selection}}
 
{{anchor|disk-selection}}
 
==== Disk selection ====
 
==== Disk selection ====
 
The user must be able to select which of the disks connected to the system will be affected by the installation process.
 
The user must be able to select which of the disks connected to the system will be affected by the installation process.
{{hidden|header=Other disks not touched|content=Disks not selected as installation targets must not be affected by the installation process in any way.|headerstyle=background:#ccccff}}
+
{{hidden|header=Other disks not touched|content=Disks not selected as installation targets must not be affected by the installation process in any way.|headerstyle=font-style:italic;color:gray|ta1=left}}
{{hidden|header=References|content=Proposed [https://lists.fedoraproject.org/pipermail/test/2012-October/110494.html 2012-10-01]. Implemented [https://lists.fedoraproject.org/pipermail/test/2012-October/110531.html 2012-10-02].|headerstyle=background:#ccccff}}
+
{{hidden|header=References|content=Proposed [https://lists.fedoraproject.org/pipermail/test/2012-October/110494.html 2012-10-01]. Implemented [https://lists.fedoraproject.org/pipermail/test/2012-October/110531.html 2012-10-02].|headerstyle=font-style:italic;color:gray|ta1=left}}
  
 
{{anchor|storage-interfaces}}
 
{{anchor|storage-interfaces}}
 
==== Storage interfaces ====
 
==== Storage interfaces ====
 
The installer must be able to complete an installation using any supported locally connected storage interface.
 
The installer must be able to complete an installation using any supported locally connected storage interface.
{{hidden|header=What are they?|content='Locally connected storage interfaces' include PATA, SATA and SCSI.|headerstyle=background:#ccccff}}
+
{{hidden|header=What are they?|content='Locally connected storage interfaces' include PATA, SATA and SCSI.|headerstyle=font-style:italic;color:gray|ta1=left}}
  
 
{{anchor|disk-layouts}}
 
{{anchor|disk-layouts}}
 
==== Disk layouts ====
 
==== Disk layouts ====
 
The installer must be able to complete an installation to a single disk using automatic partitioning.
 
The installer must be able to complete an installation to a single disk using automatic partitioning.
{{hidden|header=Details!|content=...well, so long as the disk is big enough, of course. It must work whether the disk is formatted or not and whether or not it contains any existing data - but since this is an Alpha, it's OK if it can only install to a disk with existing data by overwriting it.|headerstyle=background:#ccccff}}
+
{{hidden|header=Details!|content=...well, so long as the disk is big enough, of course. It must work whether the disk is formatted or not and whether or not it contains any existing data - but since this is an Alpha, it's OK if it can only install to a disk with existing data by overwriting it.|headerstyle=font-style:italic;color:gray|ta1=left}}
{{hidden|header=References|content=Proposed [https://lists.fedoraproject.org/pipermail/test/2012-October/110494.html 2012-10-01]. Implemented [https://lists.fedoraproject.org/pipermail/test/2012-October/110531.html 2012-10-02].|headerstyle=background:#ccccff}}
+
{{hidden|header=References|content=Proposed [https://lists.fedoraproject.org/pipermail/test/2012-October/110494.html 2012-10-01]. Implemented [https://lists.fedoraproject.org/pipermail/test/2012-October/110531.html 2012-10-02].|headerstyle=font-style:italic;color:gray|ta1=left}}
  
 
{{anchor|rescue-mode}}
 
{{anchor|rescue-mode}}

Latest revision as of 15:08, 11 March 2013

Contents

[edit] Alpha Objectives

The objectives of the Alpha release are to:

  1. Publicly release installable media versions of a feature complete test release
  2. Test accepted features of Fedora 19
  3. Identify as many F19Beta blocker bugs as possible
  4. Identify as many F19Blocker blocker bugs as possible

[edit] Alpha Release Requirements

In order to be released to the general public, the Alpha 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 judgement 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.

The term 'release-blocking desktops' means all the desktop environments in which bugs are currently considered capable of blocking a Fedora release. The current set of release-blocking desktops for the x86 architectures is GNOME and KDE, and for the ARM architectures is KDE. Note that bugs in desktops that are not part of this set which would infringe these criteria automatically qualify for freeze exception status, according to the freeze exception bug process.

The term 'release-blocking images' means all the images in which bugs are currently considered capable of blocking a Fedora release. The current set of release-blocking images includes the network install image, the DVD image, and the live images for each of the release-blocking desktops.

[edit] Process requirements

[edit] Alpha blockers CLOSED

All bugs blocking the Alpha tracker must be CLOSED.

[edit] Correct checksums

A correct checksum must be published for each official release image.

[edit] No broken packages

There must be no errors in any package on the supported images which cause the package to fail to install.

[edit] Initialization requirements

[edit] Supported images must boot

All supported images must boot in their supported configurations.

[edit] Expected image boot behavior

  • Supported dedicated installer images must boot to the expected boot menu, and then after a reasonable timeout to the installer.
  • Supported live images must boot to the expected boot menu, and then to a desktop or to a login prompt where it is clear how to log in to a desktop.

[edit] Installer requirements

Except where otherwise specified, each of these requirements applies to all supported configurations described above.

[edit] Installer must run

The installer must run when launched normally from the supported images.

[edit] Remote package sources

When using the dedicated installer images, the installer must be able to use either HTTP or FTP repositories (or both) as package sources. The network install image must default to a valid publicly-accessible package source.

[edit] DVD package source

When using the DVD image, the installer must be able to use the DVD as a package source.

[edit] Installation interfaces

When using the dedicated installer images, the installer must be able to complete an installation using the text, graphical and VNC installation interfaces.

[edit] Package sets

When doing a graphical install using the dedicated installer images, the installer must be able to install each of the release blocking desktops, as well as the minimal package set.

[edit] Disk selection

The user must be able to select which of the disks connected to the system will be affected by the installation process.

[edit] Storage interfaces

The installer must be able to complete an installation using any supported locally connected storage interface.

[edit] Disk layouts

The installer must be able to complete an installation to a single disk using automatic partitioning.

[edit] Rescue mode

The rescue mode of the installer must start successfully and be able to detect and mount an existing default installation.

[edit] Update image

The installer must be able to download and use an installer update image from an HTTP server.

[edit] Failure reporting

The installer must be able to report failures to Bugzilla, with appropriate information included.

[edit] Post-install requirements

Except where otherwise specified, each of these requirements applies to all supported configurations described above.

[edit] Expected installed system boot behavior

  • A system installed with a graphical package set must boot to the 'firstboot' utility on the first boot after installation. The firstboot utility must be able to create a working user account.
  • After firstboot is completed and on subsequent boots, a graphical install must boot to a log in screen where it is possible to log in to a working desktop as the user created during firstboot.
  • A system installed without a graphical package set must boot to a state where it is possible to log in through at least one of the default virtual consoles.

[edit] Required applications

It must be possible to run the default web browser and a terminal application from all release-blocking desktop environments.

[edit] Updates

The installed system must be able to download and install updates with yum and with the default graphical package manager in all release-blocking desktops.

[edit] Desktop background

The default desktop background must be different from that of the two previous stable releases.

[edit] Self-identification

Any component which prominently identifies a Fedora release version number, code name or milestone (Alpha, Beta, Final) must do so correctly.

[edit] System logging

A system logging infrastructure must be available, enabled by default, and working.

[edit] Shutdown

It must be possible to trigger a clean system shutdown using standard console commands.


[edit] Alpha Blocker Bugs

A bug is considered a Alpha blocker bug if any of the following criteria are met:

  • A bug in a Critical Path package that:
    • Cannot be fixed with a future stable update
    • Has a severity rating of high or greater and no reasonable workaround (see definition of severity and priority)
  • Bug hinders execution of required Alpha test plans or dramatically reduces test coverage
  • Bug relates to an unmet Alpha Release Requirement

A Fedora feature being incomplete, in and of itself, does not constitute a blocker bug. The feature process is separate from this process. Features are required to meet certain standards at certain points of the release cycle, but this is part of the feature process and managed, tracked and enforced separately from this process. However, if a proposed feature being incomplete causes any of the above criteria to be met, then the bug is a release blocker.


[edit] Contingency Plan

  • If all of the Alpha Release Requirements are not met by 20:00 ETC on Wednesday (1:00 AM UTC Thursday) the week prior to release day, the release will be delayed by one week so that the Alpha 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 Alpha 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