From Fedora Project Wiki

(add more test cases for network-attached storage)
(update iscsi test case name)
Line 64: Line 64:
* Separate 'network-attached storage' criterion was [ proposed as part of a wider revision 2011-06-23], [ implemented 2011-07-06]
* Separate 'network-attached storage' criterion was [ proposed as part of a wider revision 2011-06-23], [ implemented 2011-07-06]
* Test cases:
* Test cases:
** [[QA:Testcase_Anaconda_ISCSI_No_Authentication]]
** [[QA:Testcase_install_to_iSCSI_no_authentication]]
** [[QA:Testcase_install_to_multipath]]
** [[QA:Testcase_install_to_multipath]]
** [[QA:Testcase_install_to_FCoE_target]]
** [[QA:Testcase_install_to_FCoE_target]]

Latest revision as of 01:33, 29 March 2014

Final Objectives

The objective of the Final release is to:

  1. Provide a polished final release suitable for meeting the needs of our Target Audience

Final Release Requirements

In order to be released to the general public, a compose 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 Xfce. 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. As of Fedora 24, no 32-bit x86 image can be 'release-blocking', by FESCo policy. The canonical list of release-blocking images for Fedora 28 is on this page.

Process requirements

Beta criteria met

All Fedora 20 Beta Release Criteria must be met.

Final blockers CLOSED

All bugs blocking the Final tracker must be CLOSED.

Installer requirements

Media consistency verification

Validation of install media must work correctly for all release-blocking images.

Live image persistent overlays

The release-blocking live images must properly support mounting and using a persistent storage overlay for the entire system and/or one for the /home partition.

Package and installer sources

The installer must be able to use all supported local and remote package and installer sources.

Network attached storage

The installer must be able to detect (if possible) and install to supported network-attached storage devices.

Installation interfaces

The installer must be able to complete an installation using all supported interfaces.

Disk layouts

The installer must be able to create and install to any workable partition layout using any file system and/or container format combination offered in a default installer configuration.

Bootloader disk selection

The installer must allow the user to choose which disk the system bootloader will be installed to, and to choose not to install one at all.

Storage volume resize

Any installer mechanism for resizing storage volumes must correctly attempt the requested operation.

Windows dual boot

The installer must be able to install into free space alongside an existing clean Windows installation and, when performing a BIOS (not UEFI) installation, install a bootloader which can boot into both Windows and Fedora.

Update image

The installer must be able to use an installer update image retrieved from removable media or a remote package source.

Installer translations

The installer must correctly display all sufficiently complete translations available for use.

Virtualization requirements

Xen DomU

The release must boot successfully as Xen DomU with releases providing a functional, supported Xen Dom0 and widely used cloud providers utilizing Xen.

Post-install requirements

System services

All system services present after installation with one of the release-blocking package sets must start properly, unless they require hardware which is not present.

Critical path translations

All critical path actions on release-blocking desktops must correctly display all sufficiently complete translations available for use.

SELinux and crash notifications

There must be no SELinux denial notifications or crash notifications on boot of or during installation from a release-blocking live image, or at first login after a default install of a release-blocking desktop.

Data corruption

All known bugs that can cause corruption of user data must be fixed or documented at Common F20 bugs.

Default application functionality

All applications that can be launched using the standard graphical mechanism of a release-blocking desktop after a default installation of that desktop must start successfully and withstand a basic functionality test.

Default panel functionality

All elements of the default panel (or equivalent) configuration in all release-blocking desktops must function correctly in typical use.

Desktop keyring

Saving passwords to and retrieving passwords from the default keyring must work for all release-blocking desktops.


The proposed final Fedora artwork must be included and used as the background on release-blocking desktops. All Fedora artwork visible in critical path actions on release-blocking desktops must be consistent with the proposed final theme.

Pre-release notices

No notices or alerts about pre-release status may be shown as part of installation or critical path actions on release-blocking desktops.

Security bugs

The release must contain no known security bugs of 'important' or higher impact according to the Red Hat severity classification scale which cannot be satisfactorily resolved by a package update (e.g. issues during installation).


A Package-x-generic-16.pngspin-kickstarts package which contains the exact kickstart files used to build the release must be present in the release repository. The included kickstarts must define the correct set of release repositories.

Release notes

The final branded release notes must be present on release-blocking images and the appropriately versioned generic release notes must be available in the release repository.

Release identification

A Package-x-generic-16.pngfedora-release package containing the correct names, information and repository configuration for a final Fedora release must be present on release-blocking images and the appropriately versioned Package-x-generic-16.pnggeneric-release package must be available in the release repository.

Final Blocker Bugs

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

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 Change 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.

Contingency Plan

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

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