F19PPCBeta checklist

Beta Objectives

The objectives of the Beta release are to:

1. Publicly release installable media versions of a code complete test release: Beta is the last widely co-ordinated test release point in any given release cycle
2. Finish testing Fedora 19 Features
3. Identify as many F19PPCBlocker bugs as possible

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

Number	Requirements	Owner	Status	Comments
Process requirements
1	All criteria fromF19AlphaPPC checklist must be met.	warn dwa		* firefox crashes (only on first launch?)
2	All bugs blocking the Beta tracker must be CLOSED.
Initialization requirements
3	All release-blocking images must boot in their supported configurations. Supported media types Release-blocking dedicated installer images must boot when written to virtual media of an appropriate size (if applicable). References Test cases: QA:Testcase_Boot_Methods_Boot_Iso QA:Testcase_Boot_Methods_Dvd	pass Kick_ pass dwa	DVD.iso works netinst.iso tested by dwa
Installer requirements
4	When using the dedicated installer images, the installer must be able to use HTTP, FTP and NFS repositories as package sources. NFS specific requirements The installer can handle two different types of NFS repository. It can either contain a package tree, as with HTTP and FTP repositories, or it can contain the DVD ISO image of the same release as the installer. For Beta, only one of these types must work - if one works and the other doesn't, that is OK. Difference from Alpha This criterion differs from the similar Alpha criterion in that it requires both HTTP and FTP repositories to work (Alpha requires only one or the other), and adds the requirement for NFS repositories to work. References Test cases: 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	pass baude		nfs, ftp, http all complete
5	It must be possible to install by booting the installation kernel directly (including via yaboot and grub2) and correctly specifying a remote source for the installer itself. Remote source types All remote source types required to work for package retrieval in the relevant criterion at the current milestone must work in this case too. Incomplete remote source This must work even if the remote source is not a complete package repository but contains only the files necessary for the installer itself to run. In this case, to complete a full installation, a separate package repository would also have to be specified in some way. References Proposed 2012-04-06, implemented 2012-04-19 Test case: QA:Testcase_Boot_Methods_Pxeboot (left here for yaboot and grub2, too)	pass baude
6	The installer must be able to use all available kickstart delivery methods. 'Available' defined by installer team The intent of available is that the installer developers get to define the set of supported kickstart methods. Available kickstart delivery method means 'an argument to the ks= parameter which is backed by code in the installer'. These should be documented at Anaconda/Kickstart#Chapter_6._Making_the_Kickstart_File_Available References 'Available' rider added during major Fedora 19 criteria revision at request of anaconda team Test cases: QA:Testcase_Kickstart_Http_Server_Ks_Cfg QA:Testcase_Kickstart_File_Path_Ks_Cfg QA:Testcase_Kickstart_Hd_Device_Path_Ks_Cfg QA:Testcase_Kickstart_Nfs_Server_Path_Ks_Cfg	warn hamzy		inst.vnc fails if more than one disk is present. inst.text works.
7	When using the guided partitioning flow, the installer must be able to: Cleanly install to a disk with a valid partition table which contains existing data and sufficient unpartitioned space for a Fedora installation Complete an installation using any combination of disk configuration options it allows the user to select Remove existing storage volumes to free up space, at the user's direction Reject or disallow invalid disk and volume configurations without crashing. Cleanly install? Cleanly install' means that Fedora must be installed to the empty space, and if specified a bootloader should be installed, but otherwise the disk should be left alone: the existing disk label and partitions must be untouched and no data may be lost. Guided partitioning Guided partitioning refers to the path where the user allows the installer to handle partitioning, as opposed to custom or manual partitioning where the user has full control over the partitioning process. Disk configuration options? Disk configuration options refers to choices such as encryption and volume/partition type. References Partitioning criteria differed prior to Fedora 18 rewrite of installer GUI First attempt to revise criteria for Fedora 18 was proposed 2012-10-01, implemented 2012-10-02 Second attempt proposed 2012-10-11 after first changes seemed inadequate; never implemented Third revision made as part of major Fedora 19 criteria revision Test cases: QA:Testcase_Anaconda_autopart_(use_free_space)_install QA:Testcase_Anaconda_autopart_(reclaim)_install QA:Testcase_Anaconda_autopart_(encrypted)_install	hamzy		automatic partitioning with empty or partially empty disk works (Kick_)
8	When using the custom partitioning flow, the installer must be able to: Correctly interpret, and modify as described below, any disk with a valid 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 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 Remove a planned storage volume from the planned layout Assign sizes to newly-created storage volumes and containers Encrypt newly-created storage volumes Remove existing storage volumes Assign mount points to existing storage volumes Reject or disallow invalid disk and volume configurations without crashing. Custom partitioning Custom partitioning refers to the path where the user chooses to take full control over partitioning, as opposed to guided partitioning where the user allows the installer to handle partitioning. Re-using /home The requirement "assign mount points to existing storage volumes" is considered to cover the common operation of re-using an existing /home partition without formatting it. For all other mount points, it is acceptable if re-use requires them to be re-formatted. References Partitioning criteria differed prior to Fedora 18 rewrite of installer GUI First attempt to revise criteria for Fedora 18 was proposed 2012-10-01, implemented 2012-10-02 Second attempt proposed 2012-10-11 after first changes seemed inadequate; never implemented Third revision made as part of major Fedora 19 criteria revision Test cases: QA:Testcase_Anaconda_custom_partitioning QA:Testcase_Partitioning_On_Software_RAID	fail hamzy
9	* The installer must be able to detect and install to hardware or firmware RAID storage devices. 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. 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 Test cases: QA:Testcase_Install_to_BIOS_RAID, QA:Testcase_Install_to_Hardware_RAID	baude/hamzy/gustavold		requires special hardware
10	The installer must be able to complete a scripted installation which duplicates the default interactive installation as closely as possible. References Proposed 2011-08-23, implemented 2011-09-08 Test case: QA:Testcase_Kickstart_Http_Server_Ks_Cfg (incomplete)	pass Kick_		works fine with anaconda-ks.cfg from a previous install, just replace 'clearpart --none' with 'clearpart --linux'
11	Any installation method or process designed to run unattended must do so. There should be no prompts requiring user intervention. References Proposed 2011-03-17, implemented 2011-03-29 Test case: QA:Testcase_Kickstart_Http_Server_Ks_Cfg (incomplete)	pass Kick_
12	The rescue mode of the installer must be able to detect and mount any installation performed according to the applicable criteria, and provide a shell with access to utilities capable of performing typical recovery operations. References Test case: QA:Testcase_Anaconda_rescue_mode	pass dwa
Upgrade requirements
13	For each one of the release-blocking package sets, it must be possible to successfully complete an upgrade from a fully updated installation of the previous stable Fedora release with that package set installed. Release-blocking package sets The release-blocking package sets are the minimal set, and the sets for each one of the release-blocking desktops. Recommended upgrade mechanisms This criterion applies to the recommended upgrade mechanisms only. Upgraded system requirements The upgraded system must meet all release criteria. References Initial upgrade criterion was part of initial Fedora 13 criteria revision Adjusted to require upgraded system to work 2011-03-28 Adjusted to refer to 'officially supported upgrade mechanisms' rather than specifying particular methods: proposed 2012-09-24, implemented 2012-10-03 Wording slightly re-organized as part of the major Fedora 19 criteria revision Test cases: QA:Testcase_upgrade_fedup_cli_previous_desktop QA:Testcase_upgrade_fedup_cli_previous_kde QA:Testcase_upgrade_fedup_cli_previous_minimal QA:Testcase_upgrade_fedup_cli_previous_desktop_encrypted	pass baude		sames as primary, reboot issue
Post-install requirements Except where otherwise specified, each of these requirements applies to all supported configurations described above.
14	A system installed without a graphical package set must boot to a working login prompt without any unintended user intervention, and all virtual consoles intended to provide a working login prompt must do so. Difference from Alpha This criterion differs from the similar Alpha criterion by requiring that a login prompt be present without user intervention, and that all virtual consoles provide login prompts: the Alpha criterion is satisfied even if only a single console provides a login prompt, and it is not the one presented to the user after boot. References Requirement for graphical installs to boot to desktop was in original Fedora 13 criteria revision Changes to cover non-graphical installs were proposed 2010-08-12, implemented 2010-08-16: this included the distinct Alpha and Beta requirements Test case: QA:Testcase_base_startup	pass Kick_		only one console on PPC
15	The installed system must be able to play back sound with gstreamer-based applications. System-specific bugs System-specific bugs don't usually constitute an infringement of this criterion. It is meant to cover bugs which completely prevent sound playback from working in any hardware configuration. See Blocker_Bug_FAQ for more discussion of this. References Part of original Fedora 13 criteria revision Test case: QA:Testcase_audio_basic	pass Kick_		doesn't apply on PPC
16	No part of any release-blocking desktop's panel (or equivalent) configuration may crash on startup or be entirely non-functional. References Part of original Fedora 13 criteria revision Test case: QA:Testcase_desktop_panel_basic	pass dwa baude		gnome OK
17	Automatic mounting of removable/virtual media on insertion must work in release-blocking desktops. Removable media This criterion applies to optical discs, USB storage devices and hotpluggable eSATA hard disks, and any other similar devices that are supported. References Part of original Fedora 13 criteria revision (later broadened from 'default desktop' to 'release-blocking desktops') Test case: QA:Testcase_desktop_automount	pass Kick_		agreed on IRC that this doesn't apply on PPC with its virtual CD
18	Release-blocking desktops must notify the user of available updates, but must not do so when running as a live image. References Proposed 2010-06-24, implemented 2010-06-29 Test case: QA:Testcase_desktop_updates
19	All release-blocking desktops' offered mechanisms (if any) for shutting down, logging out and rebooting must work. Work? Similar to the Alpha criterion for shutting down, shutdown and reboot mechanisms must take storage volumes down cleanly and correctly request a shutdown or reboot from the system firmware. Logging out must return the user to the environment from which they logged in, working as expected. References Proposed 2010-06-24, implemented 2010-06-29 Test case: QA:Testcase_desktop_login	pass dwa pass Kick_		[dwa tested gnome via vnc][Kick_ tested KDE via vnc]

Beta Blocker Bugs

A bug is considered a Beta 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 Beta test plans or dramatically reduces test coverage
• Bug relates to an unmet Beta 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 Beta Release Requirements are not met by 20:00 UTC on Wednesday the week prior to release day, the release will be delayed by one week so that the Beta 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 Beta Requirements

QA has the responsibility of determining whether the criteria for the release has been met (as outlined above) through discussion with Development and Release Engineering. QA's findings will be reviewed and discussed at the Go/No-Go Meeting.

Key

See the table below for a sample format for test results. All test results are posted using the format specified Template:Result.

Test Results Format
Test Result	Explanation	Code Entered
none	Untested - This test has not been run, and is available for anyone to contribute feedback.	{{result|none}}
pass robatino	Passed - The test has been run and the tester determine the test met the expected results	{{result|pass|robatino}}
inprogress adamwill	Inprogress - An inprogress result is often used for tests that take a long time to execute. Inprogress results should be temporary and change to pass, fail or warn.	{{result|inprogress|adamwill}}
fail jlaska	Failed - Indicates a failed test. A link to a bug must be provided. See Template:Result for details on providing bug information.	{{result|fail|jlaska|XYZ|ZXY}}
warn rhe	Warning - This test completed and met the expected results of the test, but other issues were encountered during testing that warrant attention.	{{result|warn|rhe}} <ref>Brief description about the warning status</ref>
pass newgle1 warn kparal	Multiple results - More people can easily provide results to a single test case.	{{result|pass|newgle1}} {{result|warn|kparal}}

Related Pages

• Fedora Release Criteria
• Fedora 19 Alpha Release Criteria
• Fedora 19 Final Release Criteria
• Blocker Bug FAQ
• Packaging:Guidelines
• F19AlphaPPC checklist
• Architectures/PowerPC