Fedora 33 Final Release Criteria

🔗 Final Objectives

The objective of the Final release is to:

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

🔗 Process requirements

🔗 Beta criteria met

All Fedora 33 Beta Release Criteria must be met.

🔗 Final blockers CLOSED

All bugs blocking the Final tracker must be CLOSED.

🔗 Edition requirements

This section contains requirements relating to Fedora Editions: not to any specific edition, but to editions in general.

🔗 Self-identification

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.

Expand

References

• proposed 2018-01-05, implemented 2018-02-01
• Test case: QA:Testcase_base_edition_self_identification

🔗 Initialization requirements

🔗 Release-blocking images must boot

All release-blocking images must boot in their supported configurations.

Expand

Supported media types

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 officially supported methods.

Expand

Difference from Beta

This criterion differs from the similar Beta criterion only in that it requires all supported images to work when written also to optical media, not just USB sticks.

Expand

QA Testing responsibilities

According to FESCO decision ([1]), QA team is not responsible for physical optical media testing. However, if any bug is found, it'll be considered to be a blocker.

Expand

References

• demoting optical support 2016-12-06, 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

🔗 '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.

Expand

References

• Split from Basic criterion 2019-04-02
• Test case: QA:Testcase_Anaconda_User_Interface_Basic_Video_Driver

🔗 No broken packages

There must be no errors in any package on the release-blocking images which cause the package to fail to install.

Expand

What errors?

Critical errors include, but are not limited to, undeclared conflicts (explicit Conflicts: tags are acceptable) and unresolved dependencies.

Expand

Automatic blockers

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.

Expand

References

• Part of initial Fedora 13 criteria revision.
• Modification to cover errors besides conflicts and dependencies proposed 2012-12-03, implemented 2012-12-17.
• Move from Alpha to Final proposed 2017-04-05, implemented 2017-04-18.
• Test cases: QA:Testcase_Mediakit_Repoclosure, QA:Testcase_Mediakit_FileConflicts

🔗 Installer requirements

🔗 Media consistency verification

Validation of install media must work correctly for all release-blocking images.

Expand

Details

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.

Expand

References

• Proposed 2012-02-01, implemented 2012-02-20
• Re-worded 2012-06-29, extended 2012-10-24, and re-written again for major Fedora 19 criteria revision
• Test case: QA:Testcase_Mediakit_ISO_Checksums (incomplete)

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

Expand

Writing not covered

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.

Expand

References

• Proposed 2012-06-08, implemented 2012-06-29
• Test case: missing

🔗 Package and installer sources

The installer must be able to use all supported local and remote package and installer sources.

Expand

References

• 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

🔗 Network attached storage

The installer must be able to detect (if possible) and install to supported network-attached storage devices.

Expand

Supported types

Supported network-attached storage types include iSCSI, Fibre Channel and Fibre Channel over Ethernet (FCoE).

Expand

References

• iSCSI was listed along with local storage interfaces as part of initial Fedora 13 criteria revision
• Separate 'network-attached storage' criterion was proposed as part of a wider revision 2011-06-23, implemented 2011-07-06
• Test cases:
  • QA:Testcase_install_to_iSCSI_no_authentication
  • QA:Testcase_install_to_FCoE_target

🔗 Installation interfaces

The installer must be able to complete an installation using all supported interfaces.

Expand

References

• Proposed 2012-02-03, implemented 2012-02-13
• Test case: missing (all interfaces except cmdline are covered at Basic and Beta, cmdline is missing)

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

Expand

References

• Proposed 2014-12-23, implemented 2015-01-30
• Test case: QA:Testcase_Package_Sets_Minimal_Package_Install

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

Expand

Wait, what?

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

Expand

Default installer configuration?

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.

Expand

References

• 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

🔗 Firmware RAID

• The installer must be able to detect and install to firmware RAID storage devices.

Expand

System-specific bugs

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.

Expand

References

• 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 proposed 2018-09-14, implemented 2018-11-16
• Test case: QA:Testcase_Install_to_BIOS_RAID

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

Expand

References

• Added as part of major Fedora 19 criteria revision
• Test case: missing

🔗 Storage volume resize

Any installer mechanism for resizing storage volumes must correctly attempt the requested operation.

Expand

Unknown volumes

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 bug #1033778 and this mailing list thread.

Expand

What does that cover?

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.

Expand

Corruption-causing bugs covered in another criterion

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 general data corruption criterion.

Expand

References

• Proposed 2013-07-03, implemented 2013-07-10
• Test case: QA:Testcase_Anaconda_autopart_(shrink)_install (partial)

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

Expand

Clean Windows installation?

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.

Expand

Secure Boot excepted

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). cases.

Expand

References

• Part of initial Fedora 13 criteria revision
• Simplified for major Fedora 19 criteria revision to drop unnecessary 'no bootloader' clause
• [Adjusted https://lists.fedoraproject.org/pipermail/test/2014-October/123073.html 2014-10-02] to require Fedora bootloader to boot Windows even in UEFI case
• Test case: QA:Testcase_dualboot_with_windows

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

Expand

References

• Proposed 2014-08-24
• Various parties discussed the proposal and provided alternative wordings in the subsequent discussion
• Near-final form drafted by Chris Murphy 2014-09-09
• Requirement to preserve UEFI OS X boot capability proposed by Adam Williamson 2014-09-29
• Final form implemented 2014-10-06
• Test case: QA:Testcase_dualboot_with_OSX

🔗 Update image

The installer must be able to use an installer update image retrieved from removable media or a remote package source.

Expand

Supplementary to Basic

Note the corresponding Basic criterion that requires update image sourcing via HTTP to work.

Expand

References

• Proposed 2012-02-20, implemented as Beta criterion 2012-02-27, moved to Final 2012-04-04
• Test cases: QA:Testcase_Anaconda_updates.img_via_installation_source, QA:Testcase_Anaconda_updates.img_via_local_media

🔗 Installer translations

The installer must correctly display all sufficiently complete translations available for use.

Expand

Substantial breakage only

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

Expand

References

• 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

🔗 Installer help

Any element in the installer interface(s) which is clearly intended to display 'help' text must do so correctly when activated.

Expand

References

• Proposed 2015-10-31, implemented 2015-11-09
• Test case: QA:Testcase Anaconda help

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

Expand

References

• Xen requirement (referencing EC2) suggested 2011-09-26, criterion proposed 2011-10-13, implemented 2011-10-14, rewritten to an EC2-only requirement 2019-11-08
• Test cases: [[2]], [[3]] etc. as listed on Template:Cloud_test_matrix

🔗 Post-install requirements

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

Expand

References

• Proposed 2020-09-01, approved 2020-09-14, implemented 2020-09-15
• Test case: QA:Testcase base initial setup

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

Expand

References

• Part of initial Fedora 13 criteria revision
• Rewritten more specifically for major Fedora 19 criteria revision
• Test case: QA:Testcase_Services_start

🔗 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)

Expand

Switched layouts when unlocked encrypted storage

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 bug #681250

Expand

References

• Proposed 2014-01-14, implemented 2014-02-21
• Test cases: QA:Testcase_base_startup, QA:Testcase_desktop_login

🔗 Critical path translations

All critical path actions on release-blocking desktops must correctly display all sufficiently complete translations available for use.

Expand

What does this cover, exactly?

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.

Expand

References

• Proposed 2011-10-12, implemented 2011-10-14
• Test case: missing

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

Expand

Exclusions

Notifications that only happen on unusual configurations are excluded: see Blocker_Bug_FAQ.

Expand

References

• Part of initial Fedora 13 criteria revision
• Slightly revised for major Fedora 19 criteria revision
• Test case: QA:Testcase_desktop_error_checks

🔗 Data corruption

All known bugs that can cause corruption of user data must be fixed or documented at Common F33 bugs.

Expand

User data?

"User data" really means data: attempts have been made to apply this criterion to things like trivial items of configuration being reset on upgrades or the setting of the system clock, but that is not going to fly.

Expand

Fixed or documented?

If the issue is sufficiently serious, we may consider that documenting it is not sufficient and it must be fixed. This is a subjective determination that will be made at blocker review or Go/No-Go meetings.

Expand

References

• Part of initial Fedora 13 criteria revision
• Test case: N/A (a test case for this criterion is not practical, it instead covers all "known bugs")

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

Expand

Basic functionality

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.

Expand

Application types examples

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: gedit
• archive manager: file-roller
• terminal emulator: gnome-terminal
• problem reporter: abrt
• help viewer: yelp
• system settings: gnome-control-center

Expand

Determining primary applications

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 .odt file in a file manager), or to look into a favorites menu section (e.g. KDE menu -> Favorites).

Expand

References

• 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 added 2014-10-01
• Introduced application types from Fedora 33 on 2020-03-12 (KDE thread)
• Added "system settings" to blocking application types on 2020-03-26
• Test case: QA:Testcase_desktop_app_basic, QA:Testcase_desktop_app_basic_others

🔗 Default panel functionality

All elements of the default panel (or equivalent) configuration in all release-blocking desktops must function correctly in typical use.

Expand

Typical use?

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?"

Expand

References

• Part of the 'menu sanity' block of the initial Fedora 13 criteria revision
• Test case: QA:Testcase_desktop_panel_advanced

🔗 Update notification

Release-blocking desktops must notify the user of available updates, but must not do so when running as a live image.

Expand

References

• Proposed 2010-06-24, implemented 2010-06-29
• Moved from Beta to Final 2015-04-13, agreed at 2015-04-13 blocker review meeting
• Test case: QA:Testcase_desktop_update_notification

🔗 Desktop keyring

Saving passwords to and retrieving passwords from the default keyring must work for all release-blocking desktops.

Expand

References

• Part of the 'menu sanity' block of the initial Fedora 13 criteria revision
• Test case: QA:Testcase_desktop_keyring

🔗 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

Expand

'Work'?

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

Expand

References

• Printing criteria initially proposed 2019-08-20, revised text proposed 2019-02-11, implemented 2019-04-01
• Test cases: QA:Testcase_Printing_New_Printer (partially)

🔗 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 actions on release-blocking desktops must be consistent with the proposed final theme.

Expand

References

• Proposed 2010-09-10, implemented 2010-09-13
• Test case: QA:Testcase_base_artwork_release_identification

🔗 Pre-release notices

No notices or alerts about pre-release status may be shown as part of installation or critical path actions on release-blocking desktops.

Expand

Installer warning

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.

Expand

References

• Proposed 2011-11-30, implemented 2011-12-15
• Test case: missing

🔗 Security bugs

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

Expand

Determination

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.

Expand

References

• Proposed 2012-10-25, implemented 2012-11-08
• Test case: N/A (a test case for this criterion is not practical, it instead covers all "known bugs")

🔗 Kickstarts

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.

Expand

References

• Proposed 2010-10-18, implemented 2011-05-17, changed from requiring a package containing the kickstarts to be part of the release to just requiring a git tag 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)

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

Expand

References

• Proposed 2010-10-18, 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 proposed 2015-06-12, implemented 2017-06-30
• Adjusted to allow notes to be absent, but require them to be correct if present, 2017-10-26
• Test case: missing

🔗 Release identification

A fedora-release 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 generic-release package must be available in the release repository.

Expand

References

• Proposed 2010-10-18, implemented 2011-05-17
• Test case: missing

🔗 User switching

User switching must work using the mechanisms offered (if any) by all release-blocking desktops in their default configuration.

Expand

What is user switching?

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.

Expand

Work?

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 standard procedure).

Expand

Default configuration?

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.

Expand

References

• Proposed 2020-05-06 (part 2 of the discussion) after a preliminary discussion which included approval by Workstation WG
• Test case: QA:Testcase_desktop_user_switching

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

🔗 Access control

• The system must honor the controller's HBAC rules for access control.

Expand

References

• Proposed 2014-11-04, approved 2014-11-18, implemented 2014-11-20
• Test case: QA:Testcase_FreeIPA_realmd_login

🔗 Password changes

• Users with domain accounts must be able to change their passwords according to the password policy specified by the domain controller.

Expand

References

• Proposed 2014-11-04, approved 2014-11-18, implemented 2014-11-20
• Test case: QA:Testcase_FreeIPA_password_change

🔗 Single sign-on

• It must be possible for users to perform passwordless single-sign-on between two properly-configured domain clients using GSSAPI.

Expand

References

• Proposed 2014-11-04, approved 2014-11-18, implemented 2014-11-20
• Test case: FIXME

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

Expand

References

• For this specific requirement, the system need not already be enrolled as a domain client
• Proposed 2014-11-04, approved 2014-11-18, implemented 2014-11-20
• Test case: FIXME

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

Expand

References

• For this specific requirement, the system need not already be enrolled as a domain client
• Proposed 2014-11-04, approved 2014-11-18, implemented 2014-11-20
• Test case: FIXME

🔗 Server Edition requirements

These requirements apply only to the Server edition.

🔗 FreeIPA and PostgreSQL server requirements

All the additional Beta requirements for FreeIPA and PostgreSQL server systems must be met, without any workarounds being necessary.

Expand

References

• Proposed 2015-01-24, implemented 2015-02-06. Adjusted to avoid reference to Server Roles 2018-07.
• Test cases: see Beta.

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

Expand

References

• Proposed 2015-11-05, implemented 2015-11-10

🔗 IoT Edition requirements

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

Expand

References

• Test cases: QA:Testcase_Greenboot as listed on Template:General_IoT_test_matrix

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

Expand

References

• Test cases: QA:Testcase_Clevis as listed on Template:General_IoT_test_matrix

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

🔗 Related Pages

• Fedora Release Criteria
• Basic Release Criteria
• Fedora 33 Beta Release Criteria
• Blocker Bug FAQ
• QA:SOP blocker_bug process
• Automatic blockers
• Packaging:Guidelines