From Fedora Project Wiki

Revision as of 19:30, 27 June 2016 by Adamwill (talk | contribs) (create initial f25 beta criteria (copied from f24))
(diff) ← Older revision | Latest revision (diff) | Newer revision β†’ (diff)

πŸ”— 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 25 Changes
  3. Identify as many F25 Final blocker 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 42 is on this page.

πŸ”— Process requirements

πŸ”— Alpha criteria met

All Fedora 25 Alpha Release Criteria must be met.

πŸ”— Beta blockers CLOSED

All bugs blocking the Beta tracker must be CLOSED.

πŸ”— Image size requirements

The release-blocking images must meet current size requirements.

Automatic blockers

πŸ”— Initialization requirements

πŸ”— Release-blocking images must boot

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

Supported media types
Difference from Alpha

πŸ”— Installer requirements

πŸ”— Remote package sources

When using the dedicated installer images, the installer must be able to use HTTP, FTP and NFS repositories as package sources.

NFS specific requirements
Difference from Alpha

πŸ”— Direct kernel boot

It must be possible to install by booting the installation kernel directly (including via PXE) and correctly specifying a remote source for the installer itself.

Remote source types
Incomplete remote source

πŸ”— Installation interfaces

The installer must be able to complete an installation using the serial console interface.

πŸ”— Default package set

When installing with a dedicated installer image for a specific Fedora flavor, the default package set must be the correct set for that flavor.

Correct?
References

πŸ”— Package set selection

When installing with the generic network install image, interactively selecting a package set other than the default must work.

Work?
References

πŸ”— Kickstart delivery

The installer must be able to use all available kickstart delivery methods.

'Available' defined by installer team
References

πŸ”— Guided partitioning

When using the guided partitioning flow, the installer must be able to:

  • Cleanly install to a disk with a valid ms-dos or gpt disk label and 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?
Guided partitioning
Disk configuration options?
References

πŸ”— Custom partitioning

When using the custom partitioning flow, the installer must be able to:

  • 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
  • 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
Re-using /home
References

πŸ”— Hardware and firmware RAID

  • The installer must be able to detect and install to hardware or firmware RAID storage devices.
System-specific bugs
References

πŸ”— Scripted installation

The installer must be able to complete a scripted installation which duplicates the default interactive installation as closely as possible.

πŸ”— Unattended installation

Any installation method or process designed to run unattended must do so. There should be no prompts requiring user intervention.

πŸ”— Rescue mode

The rescue mode of the installer must start successfully and 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.

Start successfully?
References

πŸ”— Upgrade requirements

For each one of the release-blocking package sets, it must be possible to successfully complete a direct upgrade from fully updated installations of the last two stable Fedora releases with that package set installed.

Release-blocking package sets
Recommended upgrade mechanisms
Upgraded system requirements
References


πŸ”— Virtualization requirements

πŸ”— Self hosting virtualization

The release must be able host virtual guest instances of the same release.

What does that mean?
Recommended virtualization technology
References

πŸ”— Guest on current stable release

The release must install and boot successfully as a virtual guest in a situation where the virtual host is running the current stable Fedora release.

Recommended virtualization technology
References

πŸ”— Post-install requirements

Except where otherwise specified, each of these requirements applies to all supported configurations described above.

πŸ”— Expected installed system boot behavior

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
References

πŸ”— Working sound

The installed system must be able to play back sound with gstreamer-based applications.

System-specific bugs
References

πŸ”— Desktop panel

No part of any release-blocking desktop's panel (or equivalent) configuration may crash on startup or be entirely non-functional.

References

πŸ”— Automatic mounting

Automatic mounting of removable media on insertion must work in release-blocking desktops.

Removable media
References

πŸ”— Updates

The installed system must be able to download and install updates with the default graphical package manager in all release-blocking desktops.

Bugs in particular updates
References

πŸ”— Shutdown, reboot, logout

Shutting down, logging out and rebooting must work using standard console commands and the mechanisms offered (if any) by all release-blocking desktops.

Work?

πŸ”— Domain client requirements

These requirements apply to any system properly configured as a client of another system which is an active and correctly configured with the Server Domain Controller role.

πŸ”— User authentication

The system must be able to authenticate users against the domain controller's accounts using SSSD.

References

πŸ”— Server Product requirements

These requirements apply only to the Server product.

πŸ”— Remote logging

It must be possible to forward system logs to a remote system using Server packages.

πŸ”— Role functional requirements

The core functional requirements for all Featured Server Roles must be met, without any workarounds being necessary.

The other functional requirements for all Featured Server Roles must be met, but it is acceptable if moderate workarounds are necessary to achieve this.

Workarounds
References

πŸ”— Cockpit management interface

It must be possible to log in to the default Cockpit instance and use it to:

  • View the system's logs
  • View the system's running services
  • Enrol the system to a FreeIPA or Active Directory domain

πŸ”— Cloud Product requirements

These requirements apply only to the Cloud product.

πŸ”— Growroot

Release blocking cloud images must be able to automatically utilize all available space on a supported volume.

Supported Volumes?

πŸ”— Cloud-init

The cloud-init package must be functional for release blocking cloud images.

Functional?


πŸ”— 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.

πŸ”— Related Pages