- 1 Final Objectives
- 2 Final Release Requirements
- 2.1 Process requirements
- 2.2 Installer requirements
- 2.2.1 Media consistency verification
- 2.2.2 Live image persistent overlays
- 2.2.3 Package and installer sources
- 2.2.4 Network attached storage
- 2.2.5 Installation interfaces
- 2.2.6 Minimal install
- 2.2.7 Disk layouts
- 2.2.8 Bootloader disk selection
- 2.2.9 Storage volume resize
- 2.2.10 Windows dual boot
- 2.2.11 OS X dual boot
- 2.2.12 Update image
- 2.2.13 Installer translations
- 2.2.14 Installer help
- 2.3 Virtualization requirements
- 2.4 Post-install requirements
- 2.4.1 System services
- 2.4.2 Keyboard layout configuration
- 2.4.3 Critical path translations
- 2.4.4 SELinux and crash notifications
- 2.4.5 Data corruption
- 2.4.6 Default application functionality
- 2.4.7 Default panel functionality
- 2.4.8 Update notification
- 2.4.9 Desktop keyring
- 2.4.10 Artwork
- 2.4.11 Pre-release notices
- 2.4.12 Security bugs
- 2.4.13 Kickstarts
- 2.4.14 Release notes
- 2.4.15 Release identification
- 2.5 Domain client requirements
- 2.6 Server Product 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 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 30 is on this page.
Beta criteria met
All Fedora 24 Beta Release Criteria must be met.
Final blockers CLOSED
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.
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.
The release must boot successfully as Xen DomU with releases providing a functional, supported Xen Dom0 and widely used cloud providers utilizing Xen.
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.
All known bugs that can cause corruption of user data must be fixed or documented at Common F24 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.
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.
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.
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).
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.
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.
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.
- 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 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.
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.
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.