From Fedora Project Wiki

(template-ize the preamble to the release criteria so it doesn't get out of sync, and add a note about 'release-blocking desktops')
 
(revise and update a bit for current status quo of images and editions)
 
(16 intermediate revisions by 4 users not shown)
Line 1: Line 1:
In order to be the released to the general public, the {{{prerelease|PRE-RELEASE}}} Candidate (RC) 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.
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.
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' should be understood to mean all the desktop environments in which bugs are currently considered capable of blocking a Fedora release. The current set of release-blocking desktops is GNOME and KDE. Note that bugs in desktops that are not part of this set which would infringe these criteria automatically qualify for nice-to-have status, according to the [[QA:SOP_nth_bug_process|nice-to-have bug process]].
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 [[QA:SOP_freeze_exception_bug_process|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 [https://docs.fedoraproject.org/en-US/iot/ 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 {{FedoraVersion|long|next}} is on [https://docs.fedoraproject.org/en-US/releases/f{{FedoraVersionNumber|next}}/blocking/ this page].

Latest revision as of 22:15, 12 September 2022

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 37 is on this page.