F19AlphaPPC checklist

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(Created page with "== Alpha Objectives == The objectives of the Alpha release are to: # Publicly release installable media versions of a feature complete test release ...")
 
Line 17: Line 17:
 
!colspan="5"| Process requirements
 
!colspan="5"| Process requirements
 
|-
 
|-
 +
{{anchor|alpha-blockers-closed}}
 
| 1 || All bugs blocking the [https://bugzilla.redhat.com/showdependencytree.cgi?id=f19alpha&hide_resolved=1 Alpha tracker] must be [[BugZappers/BugStatusWorkFlow#CLOSED|CLOSED]] || || {{result|none}} ||
 
| 1 || All bugs blocking the [https://bugzilla.redhat.com/showdependencytree.cgi?id=f19alpha&hide_resolved=1 Alpha tracker] must be [[BugZappers/BugStatusWorkFlow#CLOSED|CLOSED]] || || {{result|none}} ||
 
|-
 
|-
 +
{{anchor|correct-checksums}}
 
| 2 || A correct checksum must be published for each official release image.
 
| 2 || A correct checksum must be published for each official release image.
 
{{hidden|header=References|content=
 
{{hidden|header=References|content=
Line 26: Line 28:
 
|| || {{result|none}} ||
 
|| || {{result|none}} ||
 
|-
 
|-
 +
{{anchor|no-broken-packages}}
 
| 3 || There must be no errors in any package on the release-blocking images which cause the package to fail to install.
 
| 3 || There must be no errors in any package on the release-blocking images which cause the package to fail to install.
 
{{hidden|header=What errors?|content=Critical errors include, but are not limited to, undeclared conflicts (explicit Conflicts: tags are acceptable) and unresolved dependencies.|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
 
{{hidden|header=What errors?|content=Critical errors include, but are not limited to, undeclared conflicts (explicit Conflicts: tags are acceptable) and unresolved dependencies.|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
Line 38: Line 41:
 
!colspan="5"| Initialization requirements
 
!colspan="5"| Initialization requirements
 
|-
 
|-
 +
{{anchor|release-blocking-images-must-boot}}
 
| 4 || All release-blocking images must boot in their supported configurations.
 
| 4 || All release-blocking images must boot in their supported configurations.
 
{{hidden|header=Supported architectures|content=Supported architectures are the Fedora [[Architectures#Primary_Architectures|primary architectures]].|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
 
{{hidden|header=Supported architectures|content=Supported architectures are the Fedora [[Architectures#Primary_Architectures|primary architectures]].|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
Line 56: Line 60:
 
|| || {{result|none}} ||
 
|| || {{result|none}} ||
 
|-
 
|-
 +
{{anchor|expected-image-boot-behavior}}
 
| 5 || Release-blocking dedicated installer images must boot to the expected boot menu, and then after a reasonable timeout to the installer.  
 
| 5 || Release-blocking dedicated installer images must boot to the expected boot menu, and then after a reasonable timeout to the installer.  
 
Release-blocking live images must boot to the expected boot menu, and then to a desktop or to a login prompt where it is clear how  
 
Release-blocking live images must boot to the expected boot menu, and then to a desktop or to a login prompt where it is clear how  
Line 70: Line 75:
 
|| || {{result|none}} ||
 
|| || {{result|none}} ||
 
|-
 
|-
 +
{{anchor|installer-requirements}}
 
!colspan="5"|Installer requirements
 
!colspan="5"|Installer requirements
 
Except where otherwise specified, each of these requirements applies to all supported configurations described [[#initialization-requirements|above]].
 
Except where otherwise specified, each of these requirements applies to all supported configurations described [[#initialization-requirements|above]].
 
|-
 
|-
 +
{{anchor|installer-must-run}}
 
| 6 || The installer must run when launched normally from the release-blocking images.
 
| 6 || The installer must run when launched normally from the release-blocking 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:#e5e5e5|fw1=normal|ta1=left}}
 
{{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:#e5e5e5|fw1=normal|ta1=left}}
Line 78: Line 85:
 
|| || {{result|none}} ||
 
|| || {{result|none}} ||
 
|-
 
|-
 +
{{anchor|remote-package-sources}}
 
| 7 || When using the dedicated installer images, the installer must be able to use either HTTP or FTP repositories (or both) as package sources.  
 
| 7 || 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.
 
The network install image must default to a valid publicly-accessible package source.
Line 89: Line 97:
 
|| || {{result|none}} ||
 
|| || {{result|none}} ||
 
|-
 
|-
 +
{{anchor|dvd-package-source}}
 
| 8 || When using the DVD image, the installer must be able to use the DVD as a package source.
 
| 8 || When using the DVD image, the installer must be able to use the DVD as a package source.
 
{{hidden|header=References|content=Test case: [[QA:Testcase_install_repository_DVD_default]]|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
 
{{hidden|header=References|content=Test case: [[QA:Testcase_install_repository_DVD_default]]|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
 
|| || {{result|none}} ||
 
|| || {{result|none}} ||
 
|-
 
|-
 +
{{anchor|installer-interfaces}}
 
| 9 || When using the dedicated installer images, the installer must be able to complete an installation using the text, graphical and VNC installation interfaces.
 
| 9 || 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:#e5e5e5|fw1=normal|ta1=left}}
 
{{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:#e5e5e5|fw1=normal|ta1=left}}
Line 104: Line 114:
 
|| || {{result|none}} ||
 
|| || {{result|none}} ||
 
|-
 
|-
 +
{{anchor|package-sets}}
 
| 10 || 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.
 
| 10 || 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:#e5e5e5|fw1=normal|ta1=left}}
 
{{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:#e5e5e5|fw1=normal|ta1=left}}
Line 114: Line 125:
 
|| || {{result|none}} ||
 
|| || {{result|none}} ||
 
|-
 
|-
 +
{{anchor|disk-selection}}
 
| 11 || The user must be able to select which of the disks connected to the system will be affected by the installation process.
 
| 11 || 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:#e5e5e5|fw1=normal|ta1=left}}
 
{{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:#e5e5e5|fw1=normal|ta1=left}}
Line 122: Line 134:
 
|| || {{result|none}} ||
 
|| || {{result|none}} ||
 
|-
 
|-
 +
{{anchor|storage-interfaces}}
 
| 12 || The installer must be able to complete an installation using any supported locally connected storage interface.
 
| 12 || 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:#e5e5e5|fw1=normal|ta1=left}}
 
{{hidden|header=What are they?|content='Locally connected storage interfaces' include PATA, SATA and SCSI.|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
Line 132: Line 145:
 
|| || {{result|none}} ||
 
|| || {{result|none}} ||
 
|-
 
|-
 +
{{anchor|disk-layouts}}
 
| 13 || The installer must be able to complete an installation to a single disk using automatic partitioning.
 
| 13 || 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:#e5e5e5|fw1=normal|ta1=left}}
 
{{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:#e5e5e5|fw1=normal|ta1=left}}
Line 140: Line 154:
 
|| || {{result|none}} ||
 
|| || {{result|none}} ||
 
|-
 
|-
 +
{{anchor|rescue-mode}}
 
| 14 || The rescue mode of the installer must start successfully and be able to detect and mount an existing default installation.
 
| 14 || The rescue mode of the installer must start successfully and be able to detect and mount an existing default installation.
 
{{hidden|header=Start successfully?|content='Start successfully' means it should be able to get you to a console that can interact with the mounted installation.|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
 
{{hidden|header=Start successfully?|content='Start successfully' means it should be able to get you to a console that can interact with the mounted installation.|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
Line 145: Line 160:
 
|| || {{result|none}} ||
 
|| || {{result|none}} ||
 
|-
 
|-
 +
{{anchor|update-image}}
 
| 15 || The installer must be able to download and use an [[Anaconda/Updates|installer update image]] from an HTTP server.
 
| 15 || The installer must be able to download and use an [[Anaconda/Updates|installer update image]] from an HTTP server.
 
{{hidden|header=References|content=
 
{{hidden|header=References|content=
Line 152: Line 168:
 
|| || {{result|none}} ||
 
|| || {{result|none}} ||
 
|-
 
|-
 +
{{anchor|failure-reporting}}
 
| 16 || The installer must be able to report failures to Bugzilla, with appropriate information included.
 
| 16 || The installer must be able to report failures to Bugzilla, with appropriate information included.
 
{{hidden|header=You mean, ANY failures?|content=No, silly - we mean crashes, really. This is about the crash reporting capabilities: when the installer crashes, it should pop up some dialogs that let you send a report containing data on the crash.|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
 
{{hidden|header=You mean, ANY failures?|content=No, silly - we mean crashes, really. This is about the crash reporting capabilities: when the installer crashes, it should pop up some dialogs that let you send a report containing data on the crash.|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
Line 157: Line 174:
 
|| || {{result|none}} ||
 
|| || {{result|none}} ||
 
|-
 
|-
 +
{{anchor|post-install-requirements}}
 
!colspan="5"|Post-install requirements
 
!colspan="5"|Post-install requirements
 
Except where otherwise specified, each of these requirements applies to all supported configurations described [[#initialization-requirements|above]].
 
Except where otherwise specified, each of these requirements applies to all supported configurations described [[#initialization-requirements|above]].
Line 178: Line 196:
 
|| || {{result|none}} ||
 
|| || {{result|none}} ||
 
|-
 
|-
 +
{{anchor|required-applications}}
 
| 18 || It must be possible to run the default web browser and a terminal application from all release-blocking desktop environments.
 
| 18 || It must be possible to run the default web browser and a terminal application from all release-blocking desktop environments.
 
{{hidden|header=Web browser requirements|content=The web browser must be able to download files, load extensions (if applicable), and log into [https://admin.fedoraproject.org/accounts/ FAS].|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
 
{{hidden|header=Web browser requirements|content=The web browser must be able to download files, load extensions (if applicable), and log into [https://admin.fedoraproject.org/accounts/ FAS].|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}

Revision as of 12:32, 9 April 2013

Contents

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

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 images defined by the three primary Products - Server, Workstation and Cloud - in their product requirement documents and/or technical specifications, and the KDE live image.

Process 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 images defined by the three primary Products - Server, Workstation and Cloud - in their product requirement documents and/or technical specifications, and the KDE live image.

Number Requirements Owner Status Comments
Process requirements
1 All bugs blocking the Alpha tracker must be CLOSED
none
2 A correct checksum must be published for each official release image.
none
3 There must be no errors in any package on the release-blocking images which cause the package to fail to install.
none
Initialization requirements
4 All release-blocking images must boot in their supported configurations.
none
5 Release-blocking dedicated installer images must boot to the expected boot menu, and then after a reasonable timeout to the installer.

Release-blocking 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.

none
Installer requirements

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

6 The installer must run when launched normally from the release-blocking images.
none
7 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.

none
8 When using the DVD image, the installer must be able to use the DVD as a package source.
none
9 When using the dedicated installer images, the installer must be able to complete an installation using the text, graphical and VNC installation interfaces.
none
10 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.
none
11 The user must be able to select which of the disks connected to the system will be affected by the installation process.
none
12 The installer must be able to complete an installation using any supported locally connected storage interface.
none
13 The installer must be able to complete an installation to a single disk using automatic partitioning.
none
14 The rescue mode of the installer must start successfully and be able to detect and mount an existing default installation.
none
15 The installer must be able to download and use an installer update image from an HTTP server.
none
16 The installer must be able to report failures to Bugzilla, with appropriate information included.
none
Post-install requirements

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

17 * 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.
none
18 It must be possible to run the default web browser and a terminal application from all release-blocking desktop environments.
none
19 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.
none
20 The default desktop background must be different from that of the two previous stable releases.
none
21 Any component which prominently identifies a Fedora release version number, code name or milestone (Alpha, Beta, Final) must do so correctly.
none
22 A system logging infrastructure must be available, enabled by default, and working.
none
23 It must be possible to trigger a clean system shutdown using standard console commands.
none

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 Change being incomplete, in and of itself, does not constitute a blocker bug. The Change process is separate from this process. Changes 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.

</span>

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.

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.

Related Pages