Fedora workstation 27 beta9/26/2023 ![]() ![]() QA:Testcase upgrade dnf previous workstation.QA:Testcase upgrade dnf current minimal.QA:Testcase upgrade dnf current workstation encrypted.QA:Testcase upgrade dnf current workstation.Added requirement to support skip-release upgrades (FN->FN+2):.Interpreted to require all fedup methods to work (or at least both repository and ISO file) in blocker review meeting.Wording slightly re-organized as part of the major Fedora 19 criteria revision.Adjusted to refer to 'officially supported upgrade mechanisms' rather than specifying particular methods: proposed, implemented.Adjusted to require upgraded system to work.Initial upgrade criterion was part of initial Fedora 13 criteria revision.Reject or disallow invalid disk and volume configurations without crashing.Assign mount points to existing storage volumes.Assign sizes to newly-created storage volumes and containers.Remove a planned storage volume from the planned layout.Create mount points backed by ext4 partitions, LVM volumes or btrfs volumes, or software RAID arrays at RAID levels 0, 1 and 5 containing ext4 partitions.Correctly interpret, and modify as described below, any disk with a valid ms-dos or gpt disk label and partition table containing ext4 partitions, LVM and/or btrfs volumes, and/or software RAID arrays at RAID levels 0, 1 and 5 containing ext4 partitions.When using the custom partitioning flow, the installer must be able to: QA:Testcase_Anaconda_autopart_(encrypted)_install.QA:Testcase_Anaconda_autopart_(reclaim)_install.QA:Testcase_Anaconda_autopart_(use_free_space)_install.Third revision made as part of major Fedora 19 criteria revision.Second attempt proposed after first changes seemed inadequate never implemented.First attempt to revise criteria for Fedora 18 was proposed, implemented.Partitioning criteria differed prior to Fedora 18 rewrite of installer GUI.The release-blocking images must meet current size requirements. The canonical list of release-blocking images for Fedora 39 is on this page.Īll bugs blocking the Beta tracker must be CLOSED. 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 term release-blocking images means all the images in which bugs are currently considered capable of blocking a Fedora release. 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 current set of release-blocking desktops for x86_64 is GNOME and KDE, and for aarch64 is GNOME. The term release-blocking desktops means all the desktop environments in which bugs are currently considered capable of blocking a Fedora 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. ![]() 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. 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. Optional and nice to have items should not be included in this list. Mostly met items are incomplete until they are met. This is intended to make the decision process as clear and straightforward as possible. In order to be released to the general public, a compose must meet all of the following criteria. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |