From Fedora Project Wiki

Revision as of 22:42, 3 July 2018 by Adamwill (talk | contribs) (create with original page content for reference)
(diff) ← Older revision | Latest revision (diff) | Newer revision β†’ (diff)

πŸ”— 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 x86_64 is GNOME and KDE, and for aarch64 is GNOME. 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 Editions - Server, Workstation and IoT - in their product requirement documents and/or technical specifications, the Everything network install image, key Cloud images, and the KDE live image. The canonical list of release-blocking images for Fedora 42 is on this page.

πŸ”— Process requirements

πŸ”— Beta criteria met

All Fedora 29 Beta Release Criteria must be met.

πŸ”— Final blockers CLOSED

All bugs blocking the Final tracker must be CLOSED.

πŸ”— Edition requirements

This section contains requirements relating to Fedora Editions: not to any specific edition, but to editions in general.

πŸ”— Self-identification

For each Edition, the installer must be clearly identified as that Edition in all of that Edition's installable release-blocking images. Also, for any deployment of that Edition in accordance with the rest of these criteria, the relevant fields in /etc/os-release must include the correct Edition name. Release-blocking images that are not part of any edition must not identify themselves as being part of any edition.

References

πŸ”— Initialization requirements

πŸ”— Release-blocking images must boot

All release-blocking images must boot in their supported configurations.

Supported media types
Difference from Beta

πŸ”— No broken packages

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

What errors?
Automatic blockers
References

πŸ”— Installer requirements

πŸ”— Media consistency verification

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

Details
References

πŸ”— 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.

Writing not covered
References

πŸ”— 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.

Supported types
References

πŸ”— Installation interfaces

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

References

πŸ”— Minimal install

When installing with the generic network install image with no update repositories enabled, the installer must be able to install the minimal package set.

References

πŸ”— 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.

Wait, what?
Default installer configuration?
References

πŸ”— 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.

References

πŸ”— Storage volume resize

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

Unknown volumes
What does that cover?
Corruption-causing bugs covered in another criterion

πŸ”— Windows dual boot

The installer must be able to install into free space alongside an existing clean Windows installation and install a bootloader which can boot into both Windows and Fedora.

Clean Windows installation?
Secure Boot excepted
References

πŸ”— OS X dual boot

The installer must be able to install into free space alongside an existing OS X installation, install and configure a bootloader that will boot Fedora.

References

πŸ”— Update image

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

Supplementary to Basic

πŸ”— Installer translations

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

Substantial breakage only

πŸ”— Installer help

Any element in the installer interface(s) which is clearly intended to display 'help' text must do so correctly when activated.

πŸ”— 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.

Dom0 not covered
References

πŸ”— 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.

References

πŸ”— Keyboard layout configuration

If a particular keyboard layout has been configured for the system, that keyboard layout must be used:

  • When unlocking encrypted storage volumes during boot (but see footnotes)
  • When logging in at a console
  • When logging in via the default login manager for a release-blocking desktop
  • After logging in to a release-blocking desktop, if the user account does not have its own keyboard layout configuration for that desktop (if there is such a user/desktop-specific configuration, it must be used when that user logs in to that desktop)
Switched layouts when unlocked encrypted storage

πŸ”— Critical path translations

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

What does this cover, exactly?
References

πŸ”— 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.

Exclusions
References

πŸ”— Data corruption

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

User data?
Fixed or documented?
References

πŸ”— 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.

All applications installed by default in Fedora Workstation must comply with each MUST and MUST NOT guideline in the Applications and Launchers policy.

Basic functionality
References

πŸ”— Default panel functionality

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

Typical use?
References

πŸ”— Update notification

Release-blocking desktops must notify the user of available updates, but must not do so when running as a live image.

πŸ”— Desktop keyring

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

References

πŸ”— Artwork

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.

Installer warning
References

πŸ”— 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).

Determination
References

πŸ”— Kickstarts

At the time of the release, the fedora-kickstarts git repository must have a tag matching the commit used to produce the accepted release candidate compose. The tag's name must clearly and unambiguously match the release number.

References

πŸ”— Release notes

Any release notes included in the release repositories and/or any release-blocking deliverables must be for the correct release, and approved for release by the documentation team.

References

πŸ”— Release identification

A fedora-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 generic-release package must be available in the release repository.

References

πŸ”— Domain client requirements

These requirements apply to any system properly configured as a client of another system which is an active and correctly configured with the Server Domain Controller role.

πŸ”— Access control

  • The system must honor the controller's HBAC rules for access control.

πŸ”— Password changes

  • Users with domain accounts must be able to change their passwords according to the password policy specified by the domain controller.

πŸ”— Single sign-on

  • It must be possible for users to perform passwordless single-sign-on between two properly-configured domain clients using GSSAPI.

πŸ”— Server discovery

  • When configured to use the domain controller for DNS services, the system must be able to use DNS to discover the domain controller address using SRV records.
References

πŸ”— SSH host key validation

  • When configured to use FreeIPA for host-key validation, an initial SSH connection between domain clients must not prompt the user to accept the SSH public key.
References

πŸ”— Server Product requirements

These requirements apply only to the Server product.

πŸ”— Role functional requirements

All functional requirements for all Featured Server Roles must be met, without any workarounds being necessary.

References

πŸ”— Cockpit management interface

All Cockpit functional criteria must be satisfied when the user is running any of the following platforms:

  • Mozilla Firefox as shipped in the same Fedora release
  • Google Chrome of the latest available version at compose time on the same Fedora release.
  • At least one of a) Mozilla Firefox or b) Google Chrome of the latest available version on Windows at compose time.
  • At least one of a) Mozilla Firefox or b) Google Chrome of the latest available version on OSX at compose time.

Manual testing will occur on the Firefox/Fedora platform. It will not be performed on the Chrome/Fedora platform nor any of the Windows / OSX platforms mentioned above, but if issues in code related to Fedora / Cockpit (and not third-party software such as the third-party browsers) in meeting the functional criteria are reported against those platforms, they may block the release. Workarounds to get around issues that are outside of our control (such as in third party browsers) will not be considered blockers but may be considered freeze exceptions.

References


πŸ”— 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