|
|
| (32 intermediate revisions by the same user not shown) |
| Line 1: |
Line 1: |
| == Beta Objectives ==
| | back into production. |
| The objectives of the Beta release are to:
| |
| # Publicly release installable media versions of a [[Feature_Freeze_Policy|code complete]] test release: Beta is the last widely co-ordinated test release point in any given release cycle
| |
| # Finish testing [[Releases/19/FeatureList| Fedora 19 Features]]
| |
| # Identify as many [https://bugzilla.redhat.com/showdependencytree.cgi?id=f19blocker&hide_resolved=1| F19Blocker] bugs as possible
| |
| | |
| == Beta Release Requirements ==
| |
| | |
| {{Template:Release_criteria_preamble|prerelease=Beta}}
| |
| | |
| === <span style="text-decoration:underline">Process requirements</span> ===
| |
| {{anchor|alpha-criteria-met}}
| |
| ==== Alpha criteria met ====
| |
| All [[Fedora 19 Alpha Release Criteria]] must be met.
| |
| | |
| {{anchor|beta-blockers-closed}}
| |
| ==== Beta blockers CLOSED ====
| |
| All bugs blocking the [https://bugzilla.redhat.com/showdependencytree.cgi?id=f19beta&hide_resolved=1 Beta tracker] must be [[BugZappers/BugStatusWorkFlow#CLOSED|CLOSED]].
| |
| | |
| {{anchor|image-size-requirements}}
| |
| ==== Image size requirements ====
| |
| The release-blocking images must meet current size requirements.
| |
| | |
| {{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 Alpha|content=This criterion differs from the similar [[Fedora_19_Alpha_Release_Criteria#Supported_images_must_boot|Alpha criterion]] only in that it requires ''all'' supported methods of writing a Fedora USB stick to work, not just ''any single one''.|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
| |
| | |
| {{anchor|installer-requirements}}
| |
| === <span style="text-decoration:underline">Installer requirements</span> ===
| |
| {{anchor|remote-package-sources}}
| |
| ==== Remote package sources ====
| |
| When using the dedicated installer images, the installer must be able to use HTTP, FTP and NFS repositories as package sources.
| |
| {{hidden|header=NFS specific requirements|content=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.|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
| |
| {{hidden|header=Difference from Alpha|content=This criterion differs from the similar [[Fedora_19_Alpha_Release_Criteria#remote-package-sources|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.|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
| |
| | |
| {{anchor|direct-kernel-boot}}
| |
| ==== 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.
| |
| {{hidden|header=Remote source types|content=All remote source types required to work for package retrieval in the [[#remote-package-source|relevant criterion]] at the current milestone must work in this case too.|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
| |
| {{hidden|header=Incomplete remote source|content=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.|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
| |
| | |
| {{anchor|installation-interfaces}}
| |
| ==== Installation interfaces ====
| |
| The installer must be able to complete an installation using the serial console interface.
| |
| | |
| {{anchor|kickstart-delivery}}
| |
| ==== Kickstart delivery ====
| |
| The installer must be able to use all available kickstart delivery methods.
| |
| | |
| {{anchor|guided-partitioning}}
| |
| ==== Guided partitioning ====
| |
| When using the guided partitioning flow, the installer must be able to:
| |
| * Complete an installation to a validly-formatted disk with existing data and sufficient empty space, using the empty space and installing a bootloader but leaving the existing data untouched
| |
| * 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.
| |
| {{hidden|header=Guided partitioning|content=''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.|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
| |
| {{hidden|header=Disk configuration options?|content=''Disk configuration options'' refers to choices such as encryption and volume/partition type.|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
| |
| | |
| {{anchor|custom-partitioning}}
| |
| ==== Custom partitioning ====
| |
| When using the custom partitioning flow, the installer must be able to:
| |
| * 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.
| |
| {{hidden|header=Custom partitioning|content=''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.|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
| |
| | |
| {{anchor|hardware-and-firmware-raid}}
| |
| ==== Hardware and firmware RAID ====
| |
| * The installer must be able to detect and install to hardware or 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}}
| |
| | |
| {{anchor|system-upgrade}}
| |
| ==== System upgrade ====
| |
| 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.
| |
| {{hidden|header=Release-blocking package sets|content=The release-blocking package sets are the minimal set, and the sets for each one of the release-blocking desktops.|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
| |
| {{hidden|header=Recommended upgrade mechanisms|content=This criterion applies to the [[Upgrading|recommended upgrade mechanisms]] only.|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
| |
| {{hidden|header=Upgraded system requirements|content=The upgraded system must meet all release criteria.|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
| |
| | |
| {{anchor|scripted-installation}}
| |
| ==== Scripted installation ====
| |
| The installer must be able to complete a scripted installation which duplicates the default interactive installation as closely as possible.
| |
| | |
| | |
| {{Template:Release_criteria_definition|prerelease=Beta}}
| |
| | |
| == 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 [[Engineering_Readiness_Meetings |''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 [[Engineering_Readiness_Meetings |''Go/No-Go'' Meeting]].
| |
| | |
| == Related Pages ==
| |
| | |
| * [[Fedora Release Criteria]]
| |
| * [[Fedora 19 Alpha Release Criteria]]
| |
| * [[Fedora 19 Final Release Criteria]]
| |
| * [[Blocker Bug FAQ]]
| |
| * [[Packaging:Guidelines]]
| |
| | |
| [[Category:Release Criteria]]
| |
