Final Objectives
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. 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.
| Number | Requirements | Owner | Status | Comments |
|---|---|---|---|---|
| 1 | All F19PPCBeta checklist criteria must be met | pknirsch | Reverified the majority of Beta checklist items, no regressions | |
| 2 | All bugs blocking the F19PPCBlocker tracker must be CLOSED | pknirsch | One bug in assigned, but cause was actually another one that just got closed (polkit -> mozjs17) | |
| 3 | If there is an embedded checksum in the image, it must match. If there is a related UI element displayed after booting the image, it must work and display the correct result | pknirsch | Checksum matches for TC6 | |
| 4 | The release live images must properly support mounting and using a persistent storage overlay for the entire system and/or one for the /home partition, if such an overlay or overlays have been correctly written to the medium from which the image is booted | does not apply | ||
| 5 | The installer must be able to use all supported local and remote package source options | pknirsch | Tested DVD, http, ftp and nfs | |
| 6 | The installer must be able to complete an installation using any network-attached storage devices (e.g. iSCSI, FCoE, Fibre Channel) | pknirsch | Tested iSCSI | |
| 7 | The installer must be able to complete an installation using all supported interfaces | pknirsch | Tested vd and iSCSI disks + eth interfaces, serial console + vnc | |
| 8 | The installer must be able to create and install to any workable partition layout using any file system offered in a default installer configuration, LVM, software, hardware or BIOS RAID, or combination of the above | pknirsch | Tested LVM, BTRFS, standard partitioning, software raid | |
| 9 | The installer must be able to install into free space alongside an existing clean single-partition Windows installation and either install a bootloader which can boot into the Windows installation, or leave the Windows bootloader untouched and working | does not apply | ||
| 10 | The installer must be able to use an installer update image retrieved from removable media, remote installation source and HTTP server | |||
| 11 | For each one of the release-blocking package sets ('minimal', and the package sets for each one of the release-blocking desktops), it must be possible to successfully complete an upgrade from a fully updated installation of the previous stable Fedora release with that package set installed, using all officially recommended upgrade mechanisms. The upgraded system must meet all release criteria | |||
| 12 | The release must boot successfully as Xen DomU with releases providing a functional, supported Xen Dom0 and widely used cloud providers utilizing Xen. This does not include any issues limited to the release functioning as Xen Dom0 | does not apply | ||
| 13 | All services in a default install must start properly | Kick_ |  Kick_ |
fprintd and rndg fail, that's to be expected but still not nice |
| 14 | All critical path actions on release-blocking desktop environments should correctly display all sufficiently complete translations available for use | |||
| 15 | In most cases, there must be no SELinux 'AVC: denied' messages or abrt crash notifications on initial boot and subsequent login (see Blocker_Bug_FAQ) | |||
| 16 | All known bugs that can cause corruption of user data must be fixed or documented at Common F19 bugs | |||
| 17 | Menu sanity - the following criteria refera to a default installed system, and to all release-blocking desktops | |||
| 18 | All Applications listed in the system menus (or equivalent) must have icons which have a consistent appearance and sufficiently high resolution to avoid appearing blurry | |||
| 19 | All applications listed under the Applications menu or category must start successfully | |||
| 20 | All applications listed under the Applications menu or category must withstand a basic functionality test and not crash after a few minutes of normal use. They must also have working Help and Help -> About menu items | |||
| 21 | No application may unintentionally appear twice in the menus. In particular, items under System must not appear under Applications | |||
| 22 | All elements of the default panel (or equivalent) configuration in all release-blocking desktops must function correctly in common use | |||
| 23 | Saving passwords in the desktop default keyring (if the desktop implements one), and retrieving passwords from the keyring, must work for all release-blocking desktops | |||
| 24 | The proposed final Fedora artwork must be included and enabled by default for all graphical bootloaders and the desktop background. All Fedora artwork must be consistent with the proposed final theme | |||
| 25 | No notices or alerts about pre-release status should be present | |||
| 26 | 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)" | |||
| 27 | A |
|||
| 28 | The final branded release notes from the Documentation team must be present on ISO media and the appropriately versioned generic release notes must be available in the online release repository | |||
| 29 | A |
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.
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.
Key
See the table below for a sample format for test results. All test results are posted using the format specified Template:Result.
| Test Results Format | ||
|---|---|---|
| Test Result | Explanation | Code Entered |
| Untested - This test has not been run, and is available for anyone to contribute feedback. | {{result|none}}
| |
 robatino |
Passed - The test has been run and the tester determine the test met the expected results | {{result|pass|robatino}}
|
| Inprogress - An inprogress result is often used for tests that take a long time to execute. Inprogress results should be temporary and change to pass, fail or warn. | {{result|inprogress|adamwill}}
| |
| Failed - Indicates a failed test. A link to a bug must be provided. See Template:Result for details on providing bug information. | {{result|fail|jlaska|XYZ|ZXY}}
| |
| [1] | Warning - This test completed and met the expected results of the test, but other issues were encountered during testing that warrant attention.
|
{{result|warn|rhe}} <ref>Brief description about the warning status</ref>
|
| Multiple results - More people can easily provide results to a single test case. | {{result|pass|newgle1}} {{result|warn|kparal}}
| |
