- 1 Final Objectives
- 2 Final Release Requirements
- 2.1 Process requirements
- 2.2 Edition requirements
- 2.3 Initialization requirements
- 2.4 Installer requirements
- 2.4.1 Media consistency verification
- 2.4.2 Live image persistent overlays
- 2.4.3 Package and installer sources
- 2.4.4 Network attached storage
- 2.4.5 Installation interfaces
- 2.4.6 Minimal install
- 2.4.7 Disk layouts
- 2.4.8 Firmware RAID
- 2.4.9 Bootloader disk selection
- 2.4.10 Storage volume resize
- 2.4.11 Windows dual boot
- 2.4.12 OS X dual boot
- 2.4.13 Update image
- 2.4.14 Installer translations
- 2.4.15 Installer help
- 2.5 Cloud image requirements
- 2.6 Post-install requirements
- 2.6.1 First boot experience
- 2.6.2 System services
- 2.6.3 Keyboard layout configuration
- 2.6.4 Critical path translations
- 2.6.5 SELinux and crash notifications
- 2.6.6 Default application functionality
- 2.6.7 Default panel functionality
- 2.6.8 Dual Monitor Set-Up
- 2.6.9 Update notification
- 2.6.10 Desktop keyring
- 2.6.11 Printing
- 2.6.12 Sound recording
- 2.6.13 Artwork
- 2.6.14 Pre-release notices
- 2.6.15 Security bugs
- 2.6.16 Kickstarts
- 2.6.17 Release notes
- 2.6.18 Release identification
- 2.6.19 User switching
- 2.7 Domain client requirements
- 2.8 Server Edition requirements
- 2.9 IoT Edition requirements
- 3 Final Blocker Bugs
- 4 Contingency Plan
- 5 Confirming Final Requirements
- 6 Related Pages
The objective of the Final release is to:
- 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. No desktop is release-blocking for 32-bit ARM. 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 35 is on this page.
Beta criteria met
All Fedora 35 Beta Release Criteria must be met.
Final blockers CLOSED
This section contains requirements relating to Fedora Editions: not to any specific edition, but to editions in general.
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.
Release-blocking images must boot
All release-blocking images must boot in their supported configurations.
'Basic graphics mode' boot mode behavior
The generic video driver option ('basic graphics mode' - as described in the Basic criteria) on all release-blocking installer and live images must function as intended (launching the installer or desktop and attempting to use a generic driver), and there must be no bugs that clearly prevent the installer or desktop from being reached in this configuration on all systems or on wide classes of hardware.
No broken packages
There must be no errors in any package on the release-blocking images which cause the package to fail to install.
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.
The installer must be able to complete an installation using all supported interfaces.
When installing with the generic network install image with no update repositories enabled, the installer must be able to install the minimal package set.
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.
- The installer must be able to detect and install to firmware RAID storage devices.
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 install a bootloader which can boot into both Windows and Fedora.
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.
The installer must be able to use an installer update image retrieved from removable media or a remote package source.
The installer must correctly display all sufficiently complete translations available for use.
Any element in the installer interface(s) which is clearly intended to display 'help' text must do so correctly when activated.
Cloud image requirements
Cloud images work in EC2
Release-blocking cloud disk images must be published to Amazon EC2 as AMIs, and these must boot successfully and meet other relevant release criteria on at least one KVM-based x86 instance type, at least one KVM-based aarch64 instance type, and at least one Xen-based x86 instance type.
First boot experience
If an initial setup utility is run or intended to be run after the first boot of the installed system, then it must start successfully and each page or panel of the initial setup utility should withstand a basic functionality test.
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.
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)
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.
Default application functionality
All applications that can be launched using the standard graphical mechanism after a default installation of Fedora Workstation on the x86_64 architecture must start successfully and withstand a basic functionality test.
For other release-blocking desktops (on any architecture), the requirements only apply to the following types of applications:
- web browser
- file manager
- package manager
- image viewer
- document viewer
- text editor
- archive manager
- terminal emulator
- problem reporter
- help viewer
- system settings
If there are multiple applications of the same type (e.g. several web browsers), the primary/default one must satisfy the requirements. If the primary/default application can't be determined, at least one of said applications must satisfy the requirements.
All applications installed by default in Fedora Workstation must comply with each MUST and MUST NOT guideline in the Applications and Launchers policy.
Default panel functionality
All elements of the default panel (or equivalent) configuration in all release-blocking desktops must function correctly in typical use.
Dual Monitor Set-Up
On computers using two monitors (e.g. two monitors on a desktop, or the built-in and one external monitor on a laptop), the graphical output is correctly shown on both monitors.
Release-blocking desktops must notify the user of available updates, but must not do so when running as a live image.
Saving passwords to and retrieving passwords from the default keyring must work for all release-blocking desktops.
Printing must work in release-blocking desktops on at least one printer using each of the following drivers:
- The built-in print-to-PDF driver
- The generic IPP driver
The installed system must be able to record audio using the default web browser (if applicable) and gstreamer-based applications.
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.
No notices or alerts about pre-release status may be shown as part of installation or critical path actions on release-blocking desktops.
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).
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.
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.
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 must be available in the release repository.
User switching must work using the mechanisms offered (if any) by all release-blocking desktops in their default configuration.
Domain client requirements
These requirements apply to any system properly configured as a client of another system which is an active and correctly configured FreeIPA domain controller.
- The system must honor the controller's HBAC rules for access control.
- Users with domain accounts must be able to change their passwords according to the password policy specified by the domain controller.
- It must be possible for users to perform passwordless single-sign-on between two properly-configured domain clients using GSSAPI.
- 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.
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.
Server Edition requirements
These requirements apply only to the Server edition.
FreeIPA and PostgreSQL server requirements
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.
IoT Edition requirements
The Greenboot service must be present on all images and installed by default when using the ISO installer. The service must be enabled to run on boot and function as intended.
Automatic partition decryption (Clevis)
When configured on hardware with a Trusted Platform Module (TPM), it must be possible for the Clevis utility to automatically decrypt any encrypted partitions on boot without any user intervention.
Final Blocker Bugs
A bug is considered a Final 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 Final test plans or dramatically reduces test coverage
- Bug relates to an unmet Final 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 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.
- 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.