|
|
| (7 intermediate revisions by the same user not shown) |
| Line 1: |
Line 1: |
| == Alpha Objectives ==
| | Was put into production. |
| The objectives of the Alpha release are to:
| |
| # Publicly release installable media versions of a [[Feature_Freeze_Policy|feature complete]] test release
| |
| # Test [[Releases/19/FeatureList|accepted features of {{FedoraVersion|long|19}}]]
| |
| # Identify as many [https://bugzilla.redhat.com/showdependencytree.cgi?id={{FedoraVersion|short|19}}beta&hide_resolved=1 {{FedoraVersion|short|19}}Beta blocker bugs] as possible
| |
| # Identify as many [https://bugzilla.redhat.com/showdependencytree.cgi?id={{FedoraVersion|short|19}}blocker&hide_resolved=1 {{FedoraVersion|short|19}}Blocker blocker bugs] as possible
| |
| | |
| == Alpha Release Requirements ==
| |
| | |
| {{Template:Release_criteria_preamble|prerelease=Alpha}}
| |
| | |
| === Process requirements ===
| |
| {{anchor|alpha-blockers-closed}}
| |
| ==== Alpha blockers CLOSED ====
| |
| All bugs blocking the [https://bugzilla.redhat.com/showdependencytree.cgi?id=f19alpha&hide_resolved=1 Alpha tracker] must be [[BugZappers/BugStatusWorkFlow#CLOSED|CLOSED]]
| |
| | |
| {{anchor|correct-checksums}}
| |
| ==== Correct checksums ====
| |
| A correct checksum must be published for each official release image.
| |
| | |
| {{anchor|no-broken-packages}}
| |
| ==== No broken packages ====
| |
| There must be no errors in any package on the supported media (REF) which cause the package to fail to install.
| |
| {{hidden|header=What errors?|content=Critical errors include, but are not limited to, undeclared conflicts (explicit Conflicts: tags are acceptable) and unresolved dependencies.|headerstyle=background:#ccccff}}
| |
| | |
| === Initialization requirements ===
| |
| {{anchor|supported-images-must-boot}}
| |
| ==== Supported images must boot ====
| |
| All supported images must boot in their supported configurations.
| |
| {{hidden|header=Supported architectures|content=Supported architectures are the Fedora [[Architectures#Primary_Architectures|primary architectures]].|headerstyle=background:#ccccff}}
| |
| {{hidden|header=Supported firmware types|content=Supported images must boot from all system firmware types that are commonly found on the primary architectures.|headerstyle=background:#ccccff}}
| |
| {{hidden|header=Supported media types|content=Supported 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 '''at least one''' of the [[How_to_create_and_use_Live_USB|officially supported methods]].|headerstyle=background:#ccccff}}
| |
| | |
| {{anchor|expected-boot-behavior}}
| |
| ==== Expected boot behavior ====
| |
| Supported dedicated installer images must boot to the expected boot menu, and then after a reasonable timeout to the installer. Supported live images must boot to the expected boot menu, and then to a desktop or to a login prompt where it is clear how to log in to a desktop.
| |
| {{hidden|header=Boot menu contents|content=The boot menu for all supported installer and live images should include an entry which causes both installation and the installed system to use a generic, highly compatible video driver (such as 'vesa'). This mechanism should work correctly, launching the installer or desktop and attempting to use the generic driver.|headerstyle=background:#ccccff}}
| |
| | |
| {{anchor|installer-must-run}}
| |
| ==== Installer must run ====
| |
| The installer must run when launched normally from the supported images.
| |
| {{hidden|header=Launched normally?|content='Launched normally' means from the boot menu on a dedicated installer image, and from the desktop on a live image.|headerstyle=background:#ccccff}}
| |
| | |
| # The installer must be able to use at least one of the HTTP or FTP remote package source options
| |
| # When booting from a DVD ISO image, the installer must be able to use the DVD local package source options
| |
| # The installer must be able to complete an installation using the text, graphical and VNC installation interfaces
| |
| # The installer must be able to install each of the release blocking desktops, as well as the minimal package set, with each supported installation method
| |
| # The installer must be able to complete an installation using any locally connected storage interface (e.g. PATA, SATA, SCSI etc...) with the default file system
| |
| # The installer must be able to complete an installation using automatic partitioning to any sufficiently large target disk, whether unformatted, empty, or containing any kind of existing data
| |
| # The installer must allow the user to select which of the disks connected to the system will be affected by the installation process. Disks not selected as installation targets must not be affected by the installation process in any way
| |
| # The rescue mode of the installer must start successfully and be able to detect and mount an existing default installation
| |
| # The installer must be able to download and use an [[Anaconda/Updates| installer update image]] from an HTTP server
| |
| # The installer must be able to report failures to Bugzilla and local disk, with appropriate information included
| |
| # In most cases (see [[Blocker_Bug_FAQ]]), a system installed according to any of the above criteria (or the appropriate Beta or Final criteria, when applying this criterion to those releases) must boot to the 'firstboot' utility on the first boot after installation, without unintended user intervention, unless the user explicitly chooses to boot in non-graphical mode. This includes correctly accessing any encrypted partitions when the correct passphrase is supplied. The firstboot utility must be able to create a working user account
| |
| # Following on from the previous criterion, after firstboot is completed and on subsequent boots, a system installed according to any of the above criteria (or the appropriate Beta or Final criteria, when applying this criterion to those releases) must boot to a working graphical environment without unintended user intervention. This includes correctly accessing any encrypted partitions when the correct passphrase is supplied
| |
| # When booting a system installed without a graphical environment, or when using a correct configuration setting to cause an installed system to boot in non-graphical mode, the system should boot to a state where it is possible to log in through at least one of the default virtual consoles
| |
| # It must be possible to run the default web browser and a terminal application from all release-blocking desktop environments. The web browser must be able to download files, load extensions, and log into [https://admin.fedoraproject.org/accounts/ FAS]
| |
| # The installed system must be able to download and install updates with yum and the default graphical package manager in all release-blocking desktops
| |
| # The default desktop background must be different from that of the two previous stable releases
| |
| # Any component which prominently identifies a Fedora release version number, code name or phase (Alpha, Beta, Final) must do so correctly
| |
| # A system logging infrastructure must be available and enabled by default. It must provide at least basic local file-based logging of kernel messages, and allow other components to write log messages. This must be done in accordance with relevant standards accepted by the Project
| |
| # It must be possible to trigger a system shutdown using standard console commands, and the system must shut down in such a way that storage volumes (e.g. simple partitions, LVs and PVs, RAID arrays) are taken offline safely and the system's BIOS or EFI is correctly requested to power down the system
| |
| | |
| <!--
| |
| IF we need this ... we fail
| |
| # The QA team has an installable testable Release Candidate for at least two full days (48 hours).
| |
| -->
| |
| | |
| {{Template:Release_criteria_definition|prerelease=Alpha}}
| |
| | |
| == Contingency Plan ==
| |
| * If all of the ''Alpha Release Requirements'' are not met by 20:00 ETC on Wednesday (1:00 AM UTC Thursday) the week prior to release day, the release will be delayed by one week so that the Alpha 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 Alpha 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 Beta Release Criteria]]
| |
| * [[Fedora 19 Final Release Criteria]]
| |
| * [[Blocker Bug FAQ]]
| |
| * [[Packaging:Guidelines]]
| |
| | |
| [[Category:Release Criteria]]
| |
