View source for Fedora 42 Final Release Criteria

== 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 ==

{{Template:Release_criteria_preamble|prerelease=Final}}
{{anchor|process-requirements}}
=== <span style="text-decoration:underline">Process requirements</span> ===
{{anchor|beta-criteria-met}}
==== Beta criteria met ====
All [[Fedora 42 Beta Release Criteria]] must be met.

{{anchor|final-blockers-closed}}
==== Final blockers CLOSED ====
All bugs blocking the [https://bugzilla.redhat.com/showdependencytree.cgi?id=F42FinalBlocker&hide_resolved=1 Final tracker] must be [[BugZappers/BugStatusWorkFlow#CLOSED|CLOSED]].

{{anchor|edition-requirements}}
=== <span style="text-decoration:underline">Edition requirements</span> ===
This section contains requirements relating to Fedora [[Editions]]: not to any specific edition, but to editions in general.

{{anchor|self-identification}}
==== Self-identification ====
For each [[Editions|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 {{filename|/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. The Fedora Council, as the body that defines Editions, may vote to waive this criterion at its discretion through its regular decision-making process.
{{hidden|header=References|content=
* [https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/message/CPRQ6UJMMADQAUYTHCDKNOROINGOOHRH/ proposed 2018-01-05], implemented 2018-02-01
* [https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/message/EFTMMXJYAZOW5CHBCON6UHWCUYWF34OY/ Council waiver proposed 2022-03-11], implemented 2022-03-16
* Test case: [[QA:Testcase_base_edition_self_identification]]
|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}

{{anchor|initialization-requirements}}
=== <span style="text-decoration:underline">Initialization requirements</span> ===
{{anchor|release-blocking-images-must-boot}}
==== Release-blocking images must boot ====
All release-blocking images must boot in their supported configurations.
{{hidden|header=Supported media types|content=Release-blocking live and dedicated installer images must boot when written to optical media of an appropriate size (if applicable) and when written to a USB stick with '''any''' of the [[How_to_create_and_use_Live_USB|officially supported methods]].|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
{{hidden|header=Difference from Beta|content=This criterion differs from the similar [[Fedora_42_Beta_Release_Criteria#release-blocking-images-must-boot|Beta criterion]] only in that it requires all supported images to work when written also to '''optical media''', not just USB sticks.|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
{{hidden|header=QA Testing responsibilities |content= According to FESCO decision ([https://pagure.io/fesco/issue/2303#comment-618750]), QA team is not responsible for physical optical media testing. However, if any bug is found, it'll be considered to be a  blocker.|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
{{hidden|header=References|content=
* [https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/KICRVUS3YHNTLHY47O5A2XL2C5YMCFIH/ demoting optical support 2016-12-06], [https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/thread/HLXHEB364LOLFHB2RDX6K4DFA4VJIWMF/ implementation 2017-01-17]
Test cases:
* [[QA:Testcase_Boot_Methods_Boot_Iso]]
* [[QA:Testcase_Boot_Methods_Dvd]]
* [[QA:Testcase_Live_Image_Boot]]
* [[QA:Testcase_USB_stick_Live_luc]]
* [[QA:Testcase_USB_stick_Live_litd]]
* [[QA:Testcase_USB_stick_Live_dd]]
* [[QA:Testcase_USB_stick_DVD_litd]]
* [[QA:Testcase_USB_stick_DVD_dd]]
|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}

{{anchor|basic-graphics-mode}}

==== 'Basic graphics mode' boot mode behavior ====
The generic video driver option ('basic graphics mode' - as described in [[Basic_Release_Criteria#expected-image-boot-behavior|the Basic criteria]]) on all release-blocking anaconda 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.
{{hidden|header=References|content=
* Split from Basic criterion [https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/message/6QZAKQI3MYMVF5RPUJDRZGQC6LWK2GLM/ 2019-04-02]
* Test case: [[QA:Testcase_Anaconda_User_Interface_Basic_Video_Driver]]
|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}

{{anchor|no-broken-packages}}
==== No broken packages ====
There must be no errors in any package on the release-blocking images which cause the package to fail to install.
{{hidden|header=What errors?|content=Critical errors include, but are not limited to, undeclared conflicts (explicit Conflicts: tags are acceptable) and unresolved dependencies.|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
{{hidden|header=Automatic blockers|content=Bugs that violate this criterion are usually considered "automatic blockers", they do not have to go through the review process. See [[QA:SOP_blocker_bug_process#Automatic_blockers]] for more details on the automatic blocker procedure.|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
{{hidden|header=References|content=
* Part of initial Fedora 13 criteria revision.
* Modification to cover errors besides conflicts and dependencies proposed [https://lists.fedoraproject.org/pipermail/test/2012-December/112106.html 2012-12-03], implemented 2012-12-17.
* Move from Alpha to Final proposed [https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/message/ZVJ6FRDVL5YCTYL2RPR7SOR3LMZNJT2R/ 2017-04-05], implemented 2017-04-18.
* Test cases: [[QA:Testcase_Mediakit_Repoclosure]], [[QA:Testcase_Mediakit_FileConflicts]]
|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}

{{anchor|installer-requirements}}
=== <span style="text-decoration:underline">Anaconda installer requirements</span> ===
Except where otherwise specified, each of these requirements applies to all supported configurations described [[#initialization-requirements|above]]. These requirements do not apply to images which do not use the "anaconda" installer.

{{anchor|image-consistency-verification}}
==== Media consistency verification ====
Validation of install media must work correctly for all release-blocking images.
{{hidden|header=Details|content=This means that the installer's mechanism for verifying that the install medium is intact must complete successfully if the medium is correctly written and return a legible failure message if it is not.|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
{{hidden|header=References|content=
* [https://lists.fedoraproject.org/pipermail/test/2012-February/105350.html Proposed 2012-02-01], [https://lists.fedoraproject.org/pipermail/test/2012-February/105677.html implemented 2012-02-20]
* [https://fedoraproject.org/w/index.php?title=Fedora_18_Final_Release_Criteria&diff=294172&oldid=293093 Re-worded 2012-06-29], [https://lists.fedoraproject.org/pipermail/test/2012-October/111098.html extended 2012-10-24], and re-written again for major Fedora 19 criteria revision
* Test case: [[QA:Testcase_Mediakit_ISO_Checksums]] (incomplete)
|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}

{{anchor|live-image-persistent-overlays}}
==== 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.
{{hidden|header=Writing not covered|content=This criterion does not cover the ''writing'' of the persistent overlay, as that stage is likely to be done using a stable released Fedora or other operating system and hence irrelevant to the release validation process.|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
{{hidden|header=References|content=
* [https://lists.fedoraproject.org/pipermail/test/2012-June/108450.html Proposed 2012-06-08], [https://lists.fedoraproject.org/pipermail/test/2012-June/108751.html implemented 2012-06-29]
* Test case: missing
|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}

{{anchor|package-and-installer-sources}}
==== Package and installer sources ====
The installer must be able to use all supported local and remote package and installer sources.
{{hidden|header=References|content=
* Part of initial Fedora 13 criteria revision
* Test cases:
** [[QA:Testcase_install_repository_DVD_default]]
** [[QA:Testcase_install_repository_Live_Image]]
** [[QA:Testcase_Boot_Methods_Pxeboot]]
** [[QA:Testcase_install_repository_Mirrorlist_default]]
** [[QA:Testcase_install_repository_Mirrorlist_graphical]]
** [[QA:Testcase_install_repository_HTTP/FTP_graphical]]
** [[QA:Testcase_install_repository_HTTP/FTP_variation]]
** [[QA:Testcase_install_repository_NFS_graphical]]
** [[QA:Testcase_install_repository_NFS_variation]]
** [[QA:Testcase_install_repository_NFSISO_variation]]
** [[QA:Testcase_install_repository_Hard_drive_variation]]
|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}

{{anchor|network-attached-storage}}
==== Network attached storage ====
The installer must be able to detect (if possible) and install to supported network-attached storage devices.
{{hidden|header=Supported types|content=Supported network-attached storage types include iSCSI, Fibre Channel and Fibre Channel over Ethernet (FCoE).|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
{{hidden|header=References|content=
* iSCSI was listed along with local storage interfaces as part of initial Fedora 13 criteria revision
* Separate 'network-attached storage' criterion was [https://lists.fedoraproject.org/pipermail/test/2011-June/100984.html proposed as part of a wider revision 2011-06-23], [https://lists.fedoraproject.org/pipermail/test/2011-July/101155.html implemented 2011-07-06]
* Test cases:
** [[QA:Testcase_install_to_iSCSI_no_authentication]]
** [[QA:Testcase_install_to_FCoE_target]]
|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}

{{anchor|installation-interfaces}}
==== Installation interfaces ====
The installer must be able to complete an installation using all supported interfaces.
{{hidden|header=References|content=
* [https://lists.fedoraproject.org/pipermail/test/2012-February/105383.html Proposed 2012-02-03], [https://lists.fedoraproject.org/pipermail/test/2012-February/105540.html implemented 2012-02-13]
* Test case: missing (all interfaces except cmdline are covered at Basic and Beta, cmdline is missing)
|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}

{{anchor|minimal-install}}
==== 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.
{{hidden|header=References|content=
* Proposed [https://lists.fedoraproject.org/pipermail/test/2014-December/124534.html 2014-12-23], implemented 2015-01-30
* Test case: [[QA:Testcase_Package_Sets_Minimal_Package_Install]]
|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}

{{anchor|disk-layouts}}
==== 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.
{{hidden|header=Wait, '''what'''?|content=Yeah, we know. This is a huge catch-all criterion and it's subject to a lot of on-the-fly interpretation. Broadly what it's 'meant to mean' is that you should be able to do anything sane that the Installation Destination spoke attempts to let you do, without the installer exploding or failing. We are trying to write more specific criteria covering this area, but it's not easy. Patches welcome, as the kids say...|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
{{hidden|header=Default installer configuration?|content=The ''default installer configuration'' clause specifically excludes options that only appear in the installer if you do something special to trigger them. There have been times when the installer has implemented experimental support for some new filesystem by showing it if you pass a special kernel parameter, for instance: the purpose of this clause is explicitly ''not'' to cover cases like that.|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
{{hidden|header=References|content=
* Part of initial Fedora 13 criteria revision
* Slightly contracted and abstracted for major Fedora 19 criteria revision
* Test cases:
** [[QA:Testcase_anaconda_btrfs_rootfs_on_disk_partition]]
** [[QA:Testcase_anaconda_lvmthin_rootfs_on_disk_partition]]
** [[QA:Testcase_anaconda_ext3_rootfs_on_disk_partition]]
** [[QA:Testcase_anaconda_xfs_rootfs_on_disk_partition]]
** Plus all the Basic and Beta partitioning test cases
|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}

{{anchor|firmware-raid}}
==== Firmware RAID ====
* The installer must be able to detect and install to firmware RAID storage devices.
{{hidden|header=System-specific bugs|content=System-specific bugs don't necessarily constitute an infringement of this criterion. It is not unusual that support for some specific firmware RAID controller, for instance, might be broken. In the case of such system-specific bugs, whether the bug is considered to infringe the criterion will be a subjective decision based on the severity of the bug and how common the hardware in question is considered to be. See [[Blocker_Bug_FAQ]] for more discussion of this.|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
{{hidden|header=References|content=
* Partitioning criteria differed prior to Fedora 18 rewrite of installer GUI; hardware, firmware and software RAID were combined
* Software RAID was rolled into partitioning criteria and firmware/hardware RAID left as a standalone criterion as part of major Fedora 19 criteria revision
* Firmware RAID requirement move from Beta to Final [https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/message/RYRDJ5EJOE3AJ6WQBOHDUW23QU4HL6PO/ proposed 2018-09-14], [https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/Y6TOAYFTFN5DZCEO4WHHQ6TASHEYK2QE/ implemented 2018-11-16]
* Test case: [[QA:Testcase_Install_to_BIOS_RAID]]
|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}

{{anchor|bootloader-disk-selection}}
==== 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.
{{hidden|header=References|content=
* Added as part of major Fedora 19 criteria revision
* Test case: missing
|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}

{{anchor|storage-volume-resize}}
==== Storage volume resize ====
Any installer mechanism for resizing storage volumes must correctly attempt the requested operation.
{{hidden|header=Unknown volumes|content=This criterion specifically does not require the installer to disallow resizing of unformatted volumes or volumes formatted with an unknown filesystem. Nor does it require recognition of any specific filesystems. The installer permitting destructive resizing of such 'unknown' volumes is explicitly not a violation of this criterion. See [[rhbug:1033778|bug #1033778]] and [https://www.redhat.com/archives/anaconda-devel-list/2016-February/msg00010.html this mailing list thread].|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
{{hidden|header=What does that cover?|content=This means that if the installer offers mechanisms for resizing storage volumes, then it must run the appropriate resizing tool with the appropriate parameters for the resize the user chooses (for volumes with recognized filesystems; see above footnote for behaviour with 'unknown' volumes). The reason it's worded this way is we specifically ''don't'' want to cover cases where the requested resize operation then fails for some reason - dirtily unmounted or over-fragmented partition, for instance. We only want to cover the case that the installer's resize code itself is badly broken.|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
{{hidden|header=Corruption-causing bugs covered in another criterion|content=This criterion does not necessarily cover all cases of bugs in resize mechanisms which may cause some kind of data corruption, but any such bug would be covered by the [[Fedora_42_Beta_Release_Criteria#data-corruption|general data corruption criterion]].|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
{{hidden|header=References|content=
* [https://lists.fedoraproject.org/pipermail/test/2013-July/116762.html Proposed 2013-07-03], [https://lists.fedoraproject.org/pipermail/test/2013-July/116912.html implemented 2013-07-10]
* Test case: [[QA:Testcase_Anaconda_autopart_(shrink)_install]] (partial)
|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}

{{anchor|windows-dual-boot}}
==== Windows dual boot ====
The installer must be able to install into free space alongside an existing clean Windows installation. As long as the Windows installation does not have BitLocker enabled, the installer must also install a bootloader which can boot into both Windows and Fedora.
{{hidden|header=Clean Windows installation?|content=
This is a get-out clause for cases where there's a bug caused by some weirdness or abnormality in the Windows installation; we can't plausibly undertake to support every possible Windows deployment. The expected scenario is a cleanly installed or OEM-deployed Windows installation. Issues caused by recovery or 'system' partitions may not be considered to violate this criterion, depending on the specific circumstances. This criterion is considered to cover both BIOS and UEFI cases.|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
{{hidden|header=Secure Boot excepted|content=
The bootloader entry part of this criterion does not apply when Secure Boot is enabled (because it has not yet been made to work, and fixing it is not trivial).|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
{{hidden|header=References|content=
* Part of initial Fedora 13 criteria revision
* Simplified for major Fedora 19 criteria revision to drop unnecessary 'no bootloader' clause
* [https://lists.fedoraproject.org/pipermail/test/2014-October/123073.html Adjusted 2014-10-02] to require Fedora bootloader to boot Windows even in UEFI case
* [https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/message/MZS54CA6O2CWNVFFHPOB64X6LEGX7ULY/ Adjusted 2022-09-30] to not require Windows boot from grub when BitLocker is enabled
* Test case: [[QA:Testcase_dualboot_with_windows]]
|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}

{{anchor|osx-dual-boot}}
{{anchor|macos-dual-boot}}
==== macOS dual boot ====
The installer must be able to install into free space alongside an existing macOS installation, install and configure a bootloader that will boot Fedora.
{{hidden|header=Supported hardware|content=This criterion only covers Mac devices with an Intel x86_64 processor.|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
{{hidden|header=References|content=
* [https://lists.fedoraproject.org/pipermail/test/2014-August/122496.html Proposed 2014-08-24]
* Various parties discussed the proposal and provided alternative wordings in the subsequent discussion
* Near-final form [https://lists.fedoraproject.org/pipermail/test/2014-September/122740.html drafted by Chris Murphy 2014-09-09]
* Requirement to preserve UEFI OS X boot capability [https://lists.fedoraproject.org/pipermail/test/2014-September/123012.html proposed by Adam Williamson 2014-09-29]
* Final form [https://lists.fedoraproject.org/pipermail/test/2014-October/123168.html implemented 2014-10-06]
* Renamed OS X to macOS and made it cover only x86_64 Macs [https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/thread/BVPLOVHGPQQJSKR7LDLMJNYTQKIJ3FG4/ on 2023-02-13]
* Test case: [[QA:Testcase_dualboot_with_OSX]]
|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}

{{anchor|update-image}}
==== Update image ====
The installer must be able to use an [[Anaconda/Updates|installer update image]] retrieved from removable media or a remote package source.
{{hidden|header=Supplementary to Basic|content=Note the corresponding [[Basic_Release_Criteria#update-image|Basic criterion]] that requires update image sourcing via HTTP to work.|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
{{hidden|header=References|content=
* [https://lists.fedoraproject.org/pipermail/test/2012-February/105681.html Proposed 2012-02-20], [https://lists.fedoraproject.org/pipermail/test/2012-February/105862.html implemented as Beta criterion 2012-02-27], [https://lists.fedoraproject.org/pipermail/test/2012-April/106612.html moved to Final 2012-04-04]
* Test cases: [[QA:Testcase_Anaconda_updates.img_via_installation_source]], [[QA:Testcase_Anaconda_updates.img_via_local_media]]
|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}

{{anchor|installer-translations}}
==== Installer translations ====
The installer must correctly display all sufficiently complete translations available for use.
{{hidden|header=Substantial breakage only|content=One or two translated strings not being displayed will not usually constitute a violation of this criterion (unless the ones missing are very important strings).|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
{{hidden|header=References|content=
* Added as part of major Fedora 19 criteria revision
* Test cases:
** [[QA:Testcase Arabic Language Install]]
** [[QA:Testcase Asian Language Install]]
** [[QA:Testcase Cyrillic Language Install]]
** [[QA:Testcase Non-English European Language Install]]
|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}

{{anchor|cloud-image-requirements}}
=== <span style="text-decoration:underline">Cloud image requirements</span> ===
{{anchor|ec2}}
==== 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.
{{hidden|header=References|content=
* [https://lists.fedoraproject.org/pipermail/test/2011-September/103127.html Xen requirement (referencing EC2) suggested 2011-09-26], [https://lists.fedoraproject.org/pipermail/test/2011-October/103624.html criterion proposed 2011-10-13], [https://lists.fedoraproject.org/pipermail/test/2011-October/103678.html implemented 2011-10-14], [https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org/message/74OFBLGN4WMNREPQTYWHFH5GNW4Q5BET/ rewritten to an EC2-only requirement 2019-11-08]
* Test cases: [[https://fedoraproject.org/wiki/QA:Testcase_base_startup]], [[https://fedoraproject.org/wiki/QA:Testcase_base_system_logging]] etc. as listed on [[Template:Cloud_test_matrix]]
|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}

{{anchor|post-install-requirements}}
=== <span style="text-decoration:underline">Post-install requirements</span> ===

{{anchor|first-boot-experience}}
==== 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.
{{hidden|header=References|content=
* Proposed [https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/HSUETWLZIXFKJXGQUEJ2QAOQZCDG242B/ 2020-09-01], approved [https://meetbot.fedoraproject.org/fedora-meeting/2020-09-14/fedora-qa.2020-09-14-15.01.html 2020-09-14], implemented 2020-09-15
* Test case: [[QA:Testcase base initial setup]]
|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}

{{anchor|system-services}}
==== 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.
{{hidden|header=References|content=
* Part of initial Fedora 13 criteria revision
* Rewritten more specifically for major Fedora 19 criteria revision
* Test case: [[QA:Testcase_Services_start]]
|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}

{{anchor|keyboard-layout-configuration}}
==== 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)
* In the "initial setup" utility (if applicable)
* 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)
{{hidden|header=Switched layouts when unlocked encrypted storage|content=Note that for technical reasons, 'switched' console layouts - where a special key combination switches between entering one set of characters and another, e.g. Cyrillic and Latin characters - will always be in their default mode when entering the passphrase to unlock an encrypted storage volume, and cannot be switched at that time. This situation does not constitute a violation of the criterion. See [[rhbug:681250|bug #681250]]|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
{{hidden|header=References|content=
* [https://lists.fedoraproject.org/pipermail/test/2014-January/120053.html Proposed 2014-01-14], [https://lists.fedoraproject.org/pipermail/test/2014-February/120454.html implemented 2014-02-21]
* added initial setup requirement [https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/thread/CE6QOT4TWCV6M3G5N4GABTJO3YYAMRLR/ on 2021-09-21]
* Test cases: [[QA:Testcase_base_startup]], [[QA:Testcase_desktop_login]]
|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}

{{anchor|critical-path-translations}}

==== Critical path translations ====
All [[Critical_path_package#Actions|critical path actions]] on release-blocking desktops must correctly display all sufficiently complete translations available for use.
{{hidden|header=What does this cover, exactly?|content=This criterion covers bugs that cause available translations not to be shown. It does not require that any translations at all be available: 'something is not translated to my language' cannot constitute a violation of this criterion. The "sufficiently complete" wording refers to a mechanism in Fedora which means that translations are not actually included until they reach a certain percentage of completion.|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
{{hidden|header=References|content=
* [https://lists.fedoraproject.org/pipermail/test/2011-October/103588.html Proposed 2011-10-12], [https://lists.fedoraproject.org/pipermail/test/2011-October/103679.html implemented 2011-10-14]
* Test case: missing
|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}

{{anchor|selinux-crash-notifications}}
==== 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.
{{hidden|header=Exclusions|content=Notifications that only happen on unusual configurations are excluded: see [[Blocker_Bug_FAQ#Hardware_and_local_configuration_dependent_issues|Blocker_Bug_FAQ]].|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
{{hidden|header=References|content=
* Part of initial Fedora 13 criteria revision
* Slightly revised for major Fedora 19 criteria revision
* Test case: [[QA:Testcase_desktop_error_checks]]
|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}

{{anchor|default-application-functionality}}
==== Default application functionality ====
For all release-blocking desktop / arch combinations, the following applications must start successfully and withstand a basic functionality test:

* 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.

Additionally, for Fedora Workstation on the x86_64 architecture, '''all''' applications installed by default which can be launched from the Activities menu must meet this requirement.

All applications installed by default in Fedora Workstation must comply with each MUST and MUST NOT guideline in the [[Workstation/Guidelines/Applications and Launchers|Applications and Launchers]] policy.
{{hidden|header=Basic functionality|content=''Basic functionality'' means that the app must at least be broadly capable of its most basic expected operations, and that it must not crash without user intervention or with only basic user intervention.|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
{{hidden|header=Application types examples|content=
Here are concrete ''examples'' for each application type, so that it is clear what each category contains: 
* web browser: firefox
* file manager: nautilus
* package manager: gnome-software
* image viewer: eog
* document viewer: evince
* text editor: gnome-text-editor
* archive manager: nautilus
* terminal emulator: gnome-terminal
* problem reporter: abrt
* help viewer: yelp
* system settings: gnome-control-center
|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
{{hidden|header=Determining primary applications|content=
The usual way to determine a primary/default application is to look into system configuration where default applications are set (e.g. ''gnome-control-center -> Default Applications''), or to launch the default application on an appropriate file type (e.g. double click on an <code>.odt</code> file in a file manager), or to look into a favorites menu section (e.g. ''KDE menu -> Favorites'').
|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
{{hidden|header=References|content=
* Part of the 'menu sanity' block of the initial Fedora 13 criteria revision
* Revised to reduce scope as part of major Fedora 19 criteria revision
* Workstation Apps and Launchers policy compliance requirement [https://lists.fedoraproject.org/pipermail/desktop/2014-October/010798.html added 2014-10-01]
* Introduced application types from Fedora 33 on [https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/thread/QEYDNIJQYPXZTXDMSMLF2JQLLZMZMCTM/ 2020-03-12] ([https://lists.fedoraproject.org/archives/list/kde@lists.fedoraproject.org/thread/HNXF7WCYQ7RAKMNGCIOXCBXERBAK44TK/ KDE thread])
* Added "system settings" to blocking application types on [https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/message/KOFUBAAYHA43FRNLOBXPO5FAZNJ32HQZ/ 2020-03-26]
* Test case: [[QA:Testcase_desktop_app_basic]], [[QA:Testcase_desktop_app_basic_others]]
|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}

{{anchor|default-panel-functionality}}

==== Default panel functionality ====
All elements of the default panel (or equivalent) configuration in all release-blocking desktops must function correctly in typical use.
{{hidden|header=Typical use?|content=Especially with GNOME 3 and KDE 4, 'panel (or equivalent)' covers quite a wide range of features, including some pretty advanced stuff - you could argue that all elements of GNOME network configuration are covered because there's a network icon on the top panel, for instance. The intent of the criterion is more that very prominent features of the desktop don't break easily, so there's a subjective cut-off in there which is decided in the blocker review process. The key question is "would this bug cause significant inconvenience or just a really bad first impression to a typical user or reviewer of the release?"|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
{{hidden|header=References|content=
* Part of the 'menu sanity' block of the initial Fedora 13 criteria revision
* Test case: [[QA:Testcase_desktop_panel_advanced]]
|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}

{{anchor|dual-monitor-set-up}}
==== Dual monitor setup ====
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.
{{hidden|header=References|content=
Due to a wide range of possible hardware configurations, any problem related to this criterion will be regarded as a "conditional blocker" (as described in [https://fedoraproject.org/wiki/Blocker_Bug_FAQ#What_about_hardware_and_local_configuration_dependent_issues.3F What about hardware and local configuration dependent issues.])."
|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}

{{anchor|software-install-remove-update}}
==== Installing, removing and updating software ====
The default graphical package manager for a given software type must appropriately:
* Install, remove and update software
* List locally-installed software coming from the official Fedora repositories
* List available software (possibly in categories, a curated list, etc)
* Display metadata relevant to the selected software (e.g. the description, screenshots, the size)
* Start the selected installed software
* Configure software sources by enabling/disabling pre-defined official repositories and then adjust the available software pool accordingly
* Notify the user when system updates are available (taking into account the intended frequency of such notifications)


The following must hold true:
* When multiple operations (covered by this criterion) are requested, all of them must finish correctly. (It's also valid to inform the user that a certain operation is not available at that moment, see the ''"Supported functionality and design decisions"'' note).
* The displayed state of software or software sources must not differ from their actual state. (E.g. an RPM package must not be shown as installed when it is not, a repository must not be shown as disabled or missing when it is enabled, etc).
* Usual GUI interactivity must not break operations covered by this criterion. (E.g. when the GUI allows the user to click some buttons while an operation is running, it must not break that operation).
* The package manager must never make the system enter an inconsistent or unbootable state. (E.g. damage the local software database, remove wrong system files, break the bootloader, etc).

{{hidden|header=Supported functionality and design decisions|content=
All requirements apply only if such a functionality is supported by the package manager; it does not imply that the package manager must support all this functionality. The requirements don't apply if some functionality is intentionally modified as a design decision (e.g. if some software sources can't be disabled as an intentional precaution to users breaking their system). If there is a bug violating the design decisions in one of the covered areas (e.g. a software source which is supposed to be always enabled can be disabled), it's up to the blocker review team to consider whether this bug makes the user experience or system safety considerably worse.
|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}

{{hidden|header=Systems in an inconsistent state|content=
While the package manager must not be the primary cause for breaking a system (unbootable, invalid internal structures, etc), it doesn't have to '''prevent''' these events from happening. So if there's e.g. a power outage during its operation or a package with harmful scriptlets is installed, which breaks the system, this is not the fault of the package manager and the criteria above are not considered violated. Similarly, when the package manager operates on an already broken system (e.g. with an inconsistent rpm database), the correct behavior cannot be guaranteed, and therefore the criteria also don't apply.
|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}

{{hidden|header=Refer to Basic footnotes|content=
The footnotes for the [[Basic_Release_Criteria#software-install-remove-update|similar Basic criterion covering console tools]] regarding software types, 'appropriate' behavior, scope and so on are all generally applicable to this criterion also.
|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}

{{hidden|header=References|content=
* [https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/thread/LR2FDFMOY4E55ZYBHWOOINZS27FQ6LSB/ Proposed 2021-11-03] and [https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/thread/ZH3LFVXEN7WOJDNYBNKZVXOFWCNVQNUZ/ 2022-01-22], implemented 2022-02-15
|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}

{{anchor|update-notification}}
==== Update notification ====
Release-blocking desktops must notify the user of available updates, but must not do so when running as a live image.
{{hidden|header=References|content=
* [https://lists.fedoraproject.org/pipermail/test/2010-June/091702.html Proposed 2010-06-24], [https://lists.fedoraproject.org/pipermail/test/2010-June/091777.html implemented 2010-06-29]
* Moved from Beta to Final 2015-04-13, [https://meetbot.fedoraproject.org/fedora-blocker-review/2015-04-13/f22-blocker-review.2015-04-13-16.19.html agreed at 2015-04-13 blocker review meeting]
* Test case: [[QA:Testcase_desktop_update_notification]]
|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}

{{anchor|desktop-keyring}}
==== Desktop keyring ====
Saving passwords to and retrieving passwords from the default keyring must work for all release-blocking desktops.
{{hidden|header=References|content=
* Part of the 'menu sanity' block of the initial Fedora 13 criteria revision
* Test case: [[QA:Testcase_desktop_keyring]]
|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}

{{anchor|printing}}
==== Printing ====
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
{{hidden|header='Work'?|content='Work' is defined as the printed output from a typical application matching the 'print preview' - note that differences in color reproduction are not considered 'non-working'.
|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
{{hidden|header=References|content=
* Printing criteria initially proposed [https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/message/2V6B3DSMPSUFW6IDE32MXQLQ4A4VI7LZ/ 2019-08-20], revised text proposed [https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/message/SHBBPIIZ6YQO6XROZAWOFQFWSEAPWAYB/ 2019-02-11], implemented [https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/message/AO3QDTLV7R7JYJK6CPUHOXNFKICE3F5Y/ 2019-04-01]
* Test cases: [[QA:Testcase_Printing_New_Printer]] (partially)
|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}

{{anchor|sound-recording}}
==== Sound recording ====
The installed system must be able to record audio using the default web browser (if applicable) and ''gstreamer-based'' applications.
{{hidden|header=System-specific bugs|content=System-specific bugs don't usually constitute an infringement of this criterion. It is meant to cover bugs which completely prevent sound recording from working in any hardware configuration. See [[Blocker_Bug_FAQ]] for more discussion of this.|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
{{hidden|header=References|content=
* [https://lists.fedorahosted.org/archives/list/test@lists.fedoraproject.org/thread/6X655I5WAR3SDV4YXRYQLAS6EJIOKFW2/ Proposed 2021-01-28], [https://lists.fedorahosted.org/archives/list/test@lists.fedoraproject.org/message/GIGTRQO4JQN4NJJ6PXOGT62TE6TFDGCY/ Implemented 2021-02-23]
* Test case: [https://fedoraproject.org/wiki/QA:Testcase_recording_basic QA:Testcase Recording Basic]
|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}

{{anchor|artwork}}
==== 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_package#Actions|critical path actions]] on release-blocking desktops must be consistent with the proposed final theme.
{{hidden|header=References|content=
* [https://lists.fedoraproject.org/pipermail/test/2010-September/093476.html Proposed 2010-09-10], [https://lists.fedoraproject.org/pipermail/test/2010-September/093568.html implemented 2010-09-13]
* Test case: [[QA:Testcase_base_artwork_release_identification]]
|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}

{{anchor|pre-release-notices}}
==== Pre-release notices ====
No notices or alerts about pre-release status may be shown as part of installation or [[Critical_path_package#Actions|critical path actions]] on release-blocking desktops.
{{hidden|header=Installer warning|content=This criterion mostly exists to remind us to make sure the 'this is a pre-release, it eats babies' warning in the installer gets taken out before the final release.|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
{{hidden|header=References|content=
* [https://lists.fedoraproject.org/pipermail/test/2011-November/104665.html Proposed 2011-11-30], [https://lists.fedoraproject.org/pipermail/test/2011-December/104865.html implemented 2011-12-15]
* Test case: missing
|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}

{{anchor|security-bugs}}
==== Security bugs ====
The release must contain no known security bugs of 'important' or higher impact according to the [https://access.redhat.com/security/updates/classification/ Red Hat severity classification scale] which cannot be satisfactorily resolved by a package update (e.g. issues during installation).
{{hidden|header=Determination|content=Determination of the classification of a bug can be done by those present at a blocker review or Go/No-Go meeting if necessary, but if the Fedora or Red Hat security team provides a classification, we will usually defer to their wisdom.|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
{{hidden|header=References|content=
* [https://lists.fedoraproject.org/pipermail/test/2012-October/111118.html Proposed 2012-10-25], [https://lists.fedoraproject.org/pipermail/test/2012-November/111469.html implemented 2012-11-08]
* Test case: N/A (a test case for this criterion is not practical, it instead covers all "known bugs")
|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}

{{anchor|kickstarts}}
==== Kickstarts ====
At the time of the release, the [https://pagure.io/fedora-kickstarts 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.
{{hidden|header=References|content=
* [https://lists.fedoraproject.org/pipermail/test/2010-October/094802.html Proposed 2010-10-18], [https://fedoraproject.org/w/index.php?title=Fedora_16_Final_Release_Criteria&diff=236660&oldid=236659 implemented 2011-05-17], changed from requiring a package containing the kickstarts to be part of the release to just requiring a git tag [https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/thread/X4YKEUQYAKLRGEPDJOOIMZNJZMM23CMU/ 2018-06-27]
* Test case: N/A (not part of the compose, so just releng and QA's responsibility to check it's done by release time)
|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}

{{anchor|release-notes}}
==== 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.
{{hidden|header=References|content=
* [https://lists.fedoraproject.org/pipermail/test/2010-October/094802.html Proposed 2010-10-18], [https://fedoraproject.org/w/index.php?title=Fedora_16_Final_Release_Criteria&oldid=236659 implemented 2011-05-17]
* Slightly revised as part of major Fedora 19 criteria revision
* Removal of requirement that notes be on all release-blocking media [https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/thread/XDRUNGFVA36IP6IMBHYWFTQYZYDXKSZW/ proposed 2015-06-12], implemented 2017-06-30
* Adjusted to allow notes to be absent, but require them to be correct if present, [https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/message/BVW6ZOQV4I5GDVFIYACWFKMEUXSTK4LC/ 2017-10-26]
* Test case: missing
|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}

{{anchor|release-identification}}
==== Release identification ====
A {{package|fedora-release}} package containing the correct names and information and a {{package|fedora-repos}} package containing the correct repository configuration for a final Fedora release must be present on release-blocking images and the appropriately versioned {{package|generic-release}} package must be available in the release repository.
{{hidden|header=updates-testing disabled|content=One specific expectation is that the ''updates-testing'' repository and any corresponding repositories (e.g. ''updates-testing-modular'') must be disabled.
|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
{{hidden|header=References|content=
* [https://lists.fedoraproject.org/pipermail/test/2010-October/094802.html Proposed 2010-10-18], [https://fedoraproject.org/w/index.php?title=Fedora_16_Final_Release_Criteria&diff=236660&oldid=236659 implemented 2011-05-17]
* Test case: missing
|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}

{{anchor|user-switching}}
==== User switching ====
User switching must work using the mechanisms offered (if any) by all release-blocking desktops in their default configuration.
{{hidden|header=What is user switching?|content=
User switching is a process of changing the currently presented desktop session between concurrent sessions of two or more different users. The user sessions keep running in the background, and users can switch between them repeatedly without losing any running application state.
For the purpose of this criterion, user switching doesn't include switching between different sessions of the ''same'' user.
|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
{{hidden|header=Work?|content=
The switching mechanism must correctly perform the requested operation. If the operation doesn't succeed on a subset of graphical drivers, the release blocking decision should be based on the number of affected users, the problem severity and available workarounds (as is our [[Blocker_Bug_FAQ#What about hardware and local configuration dependent issues?|standard procedure]]).
|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
{{hidden|header=Default configuration?|content=
The criterion is supposed to cover only cases where the system hasn't been modified in a substantial (and relevant) way. This excludes cases where people e.g. install multiple desktop environments, replace their display manager for a different one, tweak relevant systemd settings, or install a non-default graphics driver.
|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
{{hidden|header=References|content=
* [https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/thread/JRWNYGA4UK6EBLEDWLXBKUS3KC4V24FG/ Proposed 2020-05-06] ([https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/thread/2N26ZSA6I3MEMXSBBF2JFKJYPPQ5VR4F/ part 2 of the discussion]) after a preliminary discussion which included [https://pagure.io/fedora-workstation/issue/139 approval] by Workstation WG
* Test case: [[QA:Testcase_desktop_user_switching]]
|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}

{{anchor|window-manager}}
==== Window manager functionality ====
For each release-blocking desktop, the desktop environment must perform regular operations like windows close/resize/maximize/minimize/fullscreen (when supported/applicable), windows switching, using windows on virtual workspaces, and similar common operations as expected. Common application content such as regular application windows, video output, and games must be displayed correctly.

{{hidden|header=What does this cover?|content=
The goal of this criterion is to ensure general desktop-related functionality for different types of applications. A small number of non-working applications (caused by applications themselves or the desktop environment) is not a violation of this criterion. An example of a violation would be e.g. if a significant number of QT applications couldn't be resized (but they should be), or if all Java applications failed to display any content.
|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}

{{hidden|header=Difference from the Basic criterion?|content=
Compared to the similar [[Basic_Release_Criteria#window-manager|Basic criterion]], this covers all applications (including third-party ones), not just pre-installed ones. More window operations are required to work, e.g. the explicitly-stated virtual workspaces workflows.
|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}

{{hidden|header=References|content=
* Criterion proposed [https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/thread/UDMAC7IGJGHG4TBN32BPBCJCZOLWTDQG/ 2023-03-17], implemented 2023-04-04.
* Test case: [[QA:Testcase window manager]]
|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}


{{anchor|domain-client-requirements}}

=== <span style="text-decoration:underline">Domain client requirements</span> ===
These requirements apply to any system properly configured as a client of another system which is an active and correctly configured FreeIPA domain controller.

{{anchor|domain-access-control}}
==== Access control ====
* The system must honor the controller's HBAC rules for access control.
{{hidden|header=References|content=
* [https://lists.fedoraproject.org/pipermail/server/2014-November/001551.html Proposed 2014-11-04], [http://meetbot.fedoraproject.org/fedora-meeting-1/2014-11-18/fedora-meeting-1.2014-11-18-16.03.html approved 2014-11-18], [https://lists.fedoraproject.org/pipermail/server/2014-November/001583.html implemented 2014-11-20]
* Test case: [[QA:Testcase_FreeIPA_realmd_login]]
|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}

{{anchor|domain-password-change}}
==== Password changes ====
* Users with domain accounts must be able to change their passwords according to the password policy specified by the domain controller.
{{hidden|header=References|content=
* [https://lists.fedoraproject.org/pipermail/server/2014-November/001551.html Proposed 2014-11-04], [http://meetbot.fedoraproject.org/fedora-meeting-1/2014-11-18/fedora-meeting-1.2014-11-18-16.03.html approved 2014-11-18], [https://lists.fedoraproject.org/pipermail/server/2014-November/001583.html implemented 2014-11-20]
* Test case: [[QA:Testcase_FreeIPA_password_change]]
|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}

{{anchor|domain-sso}}
==== Single sign-on ====
* It must be possible for users to perform passwordless single-sign-on between two properly-configured domain clients using GSSAPI.
{{hidden|header=References|content=
* [https://lists.fedoraproject.org/pipermail/server/2014-November/001551.html Proposed 2014-11-04], [http://meetbot.fedoraproject.org/fedora-meeting-1/2014-11-18/fedora-meeting-1.2014-11-18-16.03.html approved 2014-11-18], [https://lists.fedoraproject.org/pipermail/server/2014-November/001583.html implemented 2014-11-20]
* Test case: FIXME
|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}

{{anchor|domain-server-discovery}}
==== 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.
{{hidden|header=References|content=
* For this specific requirement, the system need not already be enrolled as a domain client
* [https://lists.fedoraproject.org/pipermail/server/2014-November/001551.html Proposed 2014-11-04], [http://meetbot.fedoraproject.org/fedora-meeting-1/2014-11-18/fedora-meeting-1.2014-11-18-16.03.html approved 2014-11-18], [https://lists.fedoraproject.org/pipermail/server/2014-November/001583.html implemented 2014-11-20]
* Test case: FIXME
|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}

{{anchor|domain-ssh-validation}}
==== 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.
{{hidden|header=References|content=
* For this specific requirement, the system need not already be enrolled as a domain client
* [https://lists.fedoraproject.org/pipermail/server/2014-November/001551.html Proposed 2014-11-04], [http://meetbot.fedoraproject.org/fedora-meeting-1/2014-11-18/fedora-meeting-1.2014-11-18-16.03.html approved 2014-11-18], [https://lists.fedoraproject.org/pipermail/server/2014-November/001583.html implemented 2014-11-20]
* Test case: FIXME
|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}

{{anchor|server-edition-requirements}}
=== <span style="text-decoration:underline">[[Server]] Edition requirements</span> ===
These requirements apply only to the Server edition.

{{anchor|role-functional-requirements}}
==== FreeIPA and PostgreSQL server requirements ====
All the additional Beta requirements for [[Fedora_42_Beta_Release_Criteria#freeipa_server_requirements|FreeIPA]] and [[Fedora_42_Beta_Release_Criteria#postgresql_server_requirements|PostgreSQL]] server systems must be met, without any workarounds being necessary.
{{hidden|header=References|content=
* Proposed [https://lists.fedoraproject.org/pipermail/server/2015-January/001719.html 2015-01-24], implemented 2015-02-06. Adjusted to avoid reference to Server Roles 2018-07.
* Test cases: see Beta.
|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}

==== 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.

{{hidden|header=References|content=
* Proposed [https://lists.fedoraproject.org/pipermail/server/2015-November/002114.html 2015-11-05], implemented [http://meetbot.fedoraproject.org/fedora-meeting-1/2015-11-10/serversig.2015-11-10-16.02.html 2015-11-10]
|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}

{{anchor|IoT-Edition-requirements}}
=== <span style="text-decoration:underline">IoT Edition requirements</span> ===

{{anchor|greenboot-service}}
==== Greenboot service ====
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.
{{hidden|header=References|content=
* Test cases: [[QA:Testcase_Greenboot]] as listed on [[Template:General_IoT_test_matrix]]
|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}

{{anchor|automatic-partition-decryption}}
==== 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.
{{hidden|header=References|content=
* Test cases: [[QA:Testcase_Clevis]] as listed on [[Template:General_IoT_test_matrix]]
|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}


{{Template:Release_criteria_definition|prerelease=Final}}

== 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 [[Engineering_Readiness_Meetings |''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 [[Engineering_Readiness_Meetings |''Go/No-Go'' Meeting]].

== Related Pages ==

* [[Fedora Release Criteria]]
* [[Basic Release Criteria]]
* [[Fedora 42 Beta Release Criteria]]
* [[Blocker Bug FAQ]]
* [[QA:SOP blocker_bug process]]
* [[QA:SOP blocker_bug process#Automatic_blockers|Automatic blockers]]
* [[Packaging:Guidelines]]

[[Category:Release Criteria]]