|
|
| Line 1: |
Line 1: |
| == Alpha Objectives ==
| | #REDIRECT [[Fedora_21_Alpha_Release_Criteria]] |
| The objectives of the Alpha release are to:
| |
| # Publicly release installable media versions of a [[Feature_Freeze_Policy|feature complete]] test release | |
| # Test [[Releases/21/ChangeSet|accepted Changes of {{FedoraVersion|long|21}}]]
| |
| # Identify as many [https://bugzilla.redhat.com/showdependencytree.cgi?id={{FedoraVersion|short|21}}BetaBlocker&hide_resolved=1 {{FedoraVersion|short|21}} Beta blocker bugs] as possible
| |
| # Identify as many [https://bugzilla.redhat.com/showdependencytree.cgi?id={{FedoraVersion|short|21}}FinalBlocker&hide_resolved=1 {{FedoraVersion|short|21}} Final blocker bugs] as possible
| |
| | |
| == Alpha Release Requirements ==
| |
| {{Template:Release_criteria_preamble|prerelease=Alpha}}
| |
| | |
| === <span style="text-decoration:underline">Process requirements</span> ===
| |
| {{anchor|alpha-blockers-closed}}
| |
| ==== Alpha blockers CLOSED ====
| |
| All bugs blocking the [https://bugzilla.redhat.com/showdependencytree.cgi?id={{FedoraVersion|short|21}}AlphaBlocker&hide_resolved=1 Alpha tracker] must be [[BugZappers/BugStatusWorkFlow#CLOSED|CLOSED]].
| |
| | |
| {{anchor|fesco-blockers-fixed}}
| |
| ==== FESCo blocker bugs ====
| |
| All bugs deemed by FESCo to block the milestone release must be fixed.
| |
| {{hidden|header=Milestone release?|content=This criterion simply means that issues FESCo deems as blocking Alpha must be fixed for Alpha, issues deemed as blocking Beta must be fixed for Beta, and issues deemed as blocking Final must be fixed for Final.|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
| |
| {{hidden|header=References|content=
| |
| * [https://lists.fedoraproject.org/pipermail/test/2013-June/116531.html Proposed 2013-06-21], [https://lists.fedoraproject.org/pipermail/test/2013-July/116738.html implemented 2013-07-02]
| |
| * In practice FESCo has always been able to simply ''deem'' bugs as needing to be fixed, but there was no mechanism in place for enforcing such decisions. This criterion allows them to be enforced through the [[QA:SOP_blocker_bug_process|blocker bug process]].
| |
| |headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
| |
| | |
| {{anchor|correct-checksums}}
| |
| ==== Correct checksums ====
| |
| A correct checksum must be published for each official release image.
| |
| {{hidden|header=References|content=
| |
| * [https://lists.fedoraproject.org/pipermail/test/2012-January/105257.html Proposed 2012-01-30], [https://lists.fedoraproject.org/pipermail/test/2012-February/105677.html implemented 2012-02-20]
| |
| * Test case: [[QA:Testcase_Mediakit_ISO_Checksums]]
| |
| |headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
| |
| | |
| {{anchor|no-broken-packages}}
| |
| ==== No broken packages ====
| |
| There must be no errors in any package on the release-blocking images 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:#e5e5e5|fw1=normal|ta1=left}}
| |
| {{hidden|header=References|content=
| |
| * Part of initial Fedora 13 criteria revision.
| |
| * Modification to cover errors besides conflicts and dependencies proposed [https://lists.fedoraproject.org/pipermail/test/2012-December/112106.html 2012-12-03], implemented 2012-12-17.
| |
| * Test cases: [[QA:Testcase_Mediakit_Repoclosure]], [[QA:Testcase_Mediakit_FileConflicts]]
| |
| |headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
| |
| | |
| {{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 architectures|content=Supported architectures are the Fedora [[Architectures#Primary_Architectures|primary architectures]]. All images are not necessarily expected to be available for all primary architectures.|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
| |
| {{hidden|header=Supported firmware types|content=Release-blocking images must boot from all system firmware types that are commonly found on the primary architectures.|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
| |
| {{hidden|header=Supported ARM platforms|content=Supported ARM platforms are those listed by the ARM team at [[Architectures/ARM/Supported_Platforms]].|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
| |
| {{hidden|header=Supported cloud environments|content=Release-blocking cloud images must boot in the [[Infrastructure/FedoraCloud|Fedora OpenStack Cloud]] and in [https://aws.amazon.com/ec2/ Amazon EC2].|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
| |
| {{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 '''at least one''' of the [[How_to_create_and_use_Live_USB|officially supported methods]]. Release-blocking ARM disk images must boot when written to a medium bootable by the platform under test, according to the instructions for the platform under test.|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
| |
| {{hidden|header=System-specific bugs|content=System-specific bugs don't necessarily constitute an infringement of this criterion - for instance, if the image fails to boot because of a bug in some specific system's firmware, that is unlikely to constitute a violation unless the system is an extremely popular one. See [[Blocker_Bug_FAQ]] for more discussion of this.|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
| |
| {{hidden|header=References|content=
| |
| Test cases:
| |
| * [[QA:Testcase_Boot_default_install]]
| |
| * [[QA:Testcase_USB_stick_Live_luc]]
| |
| * [[QA:Testcase_USB_stick_Live_litd]]
| |
| * [[QA:Testcase_USB_stick_Live_dd]]
| |
| * [[QA:Testcase_USB_stick_DVD_litd]]
| |
| * [[QA:Testcase_USB_stick_DVD_dd]]
| |
| |headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
| |
| | |
| {{anchor|expected-image-boot-behavior}}
| |
| ==== Expected image boot behavior ====
| |
| * Release-blocking dedicated installer images must boot to the expected boot menu, and then after a reasonable timeout to the installer.
| |
| * Release-blocking 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.
| |
| * Release-blocking ARM disk images must boot to the initial-setup utility.
| |
| * Release-blocking cloud images must allow login with the user authentication configuration requested during instance creation.
| |
| {{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:#e5e5e5|fw1=normal|ta1=left}}
| |
| {{hidden|header=System-specific bugs|content=System-specific bugs don't necessarily constitute an infringement of this criterion - for instance, if the installer or desktop fails to start because of a bug in support for some specific graphics card, that is unlikely to constitute a violation. See [[Blocker_Bug_FAQ]] for more discussion of this.|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
| |
| {{hidden|header=References|content=
| |
| * [[rhbug:614488|Bugzilla: #614488]] was proposed as Alpha blocker for F14. Bug was fixed before before blocker status was confirmed or rejected.
| |
| * Proposed [https://lists.fedoraproject.org/pipermail/test/2010-July/092148.html 2010-07-16].
| |
| * Implemented [https://lists.fedoraproject.org/pipermail/test/2010-July/092231.html 2010-07-23].
| |
| * Rewritten as part of major Fedora 19 criteria revision.
| |
| * Test cases: see test cases for [[#release-blocking-images-must-boot|"Release-blocking images must boot"]]
| |
| |headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
| |
| | |
| {{anchor|installer-requirements}}
| |
| === <span style="text-decoration:underline">Installer requirements</span> ===
| |
| Except where otherwise specified, each of these requirements applies to all supported configurations described [[#initialization-requirements|above]]. These requirements do not apply to images which do not use the installer.
| |
| | |
| {{anchor|installer-must-run}}
| |
| ==== Installer must run ====
| |
| The installer must run when launched normally from the release-blocking 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:#e5e5e5|fw1=normal|ta1=left}}
| |
| {{hidden|header=References|content=Test cases: see test cases for [[#release-blocking-images-must-boot|"Release-blocking images must boot"]]|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
| |
| | |
| {{anchor|remote-package-sources}}
| |
| ==== Remote package sources ====
| |
| When using the dedicated installer images, the installer must be able to use either HTTP or FTP repositories (or both) as package sources. The network install image must default to a valid publicly-accessible package source.
| |
| {{hidden|header=References|content=
| |
| 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]]
| |
| |headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
| |
| | |
| {{anchor|dvd-package-source}}
| |
| ==== Media package source ====
| |
| When using a dedicated installer image that contains packages, the installer must be able to use the install medium as a package source.
| |
| {{hidden|header=References|content=Test case: [[ QA:Testcase_Boot_default_install]]|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
| |
| | |
| {{anchor|installer-interfaces}}
| |
| ==== Installation interfaces ====
| |
| When using a dedicated installer image, the installer must be able to complete an installation using the text, graphical and VNC installation interfaces.
| |
| {{hidden|header=Showstoppers|content=This criterion covers showstopper bugs in the installer for which there isn't any other specific criterion: obviously, it can't 'complete an installation' if there's a showstopper. However, it does not mean that any failed installation test at all constitutes a release blocking issue: an installer which works fine in most cases but crashes when you attach it to a Hitachi hard disk on a wet Thursday is still 'able to complete an installation'.|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
| |
| {{hidden|header=References|content=
| |
| Test cases:
| |
| * [[QA:Testcase_Anaconda_User_Interface_Graphical]]
| |
| * [[QA:Testcase_Anaconda_User_Interface_Text]]
| |
| * [[QA:Testcase_Anaconda_User_Interface_VNC]]
| |
| * [[QA:Testcase_Anaconda_User_Interface_VNC_Vncconnect]]
| |
| |headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
| |
| | |
| {{anchor|package-sets}}
| |
| ==== Package sets ====
| |
| When doing a graphical install using the dedicated installer images, the installer must be able to install each of the release blocking desktops, as well as the minimal package set.
| |
| {{hidden|header=Not all at once!|content=This means you must be able to do a GNOME install, then start over and do a KDE install, then start over and do a minimal install. Not necessarily that you should be able to do any combination of them all at once.|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
| |
| {{hidden|header=Supplementary groups not included|content=This criterion does not cover all the supplementary groups the installer interface may offer for the release-blocking desktops; it only covers the desktop package sets themselves. This clarification was requested in [[rhbug:959696||bug #959696]].|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
| |
| {{hidden|header=References|content=
| |
| * Modification from 'default package set' proposed [https://lists.fedoraproject.org/pipermail/test/2012-September/109860.html 2012-09-06].
| |
| * Idea to cover the release blocking desktops and minimal package set proposed [https://lists.fedoraproject.org/pipermail/test/2012-September/109862.html 2012-09-06], implemented 2012-09-26.
| |
| * Note that the 'default package set' was later restored to the installer, but this criterion was still considered to be an improvement, and kept.
| |
| * Test cases:
| |
| ** [[QA:Testcase_Package_Sets_Default_Package_Install]]
| |
| ** [[QA:Testcase_Package_Sets_Minimal_Package_Install]]
| |
| ** [[QA:Testcase_Package_Sets_KDE_Package_Install]]
| |
| |headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
| |
| | |
| {{anchor|disk-selection}}
| |
| ==== Disk selection ====
| |
| The user must be able to select which of the disks connected to the system will be affected by the installation process.
| |
| {{hidden|header=Other disks not touched|content=Disks not selected as installation targets must not be affected by the installation process in any way.|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
| |
| {{hidden|header=References|content=
| |
| * Proposed [https://lists.fedoraproject.org/pipermail/test/2012-October/110494.html 2012-10-01], implemented [https://lists.fedoraproject.org/pipermail/test/2012-October/110531.html 2012-10-02].
| |
| * Test case: [[QA:Testcase_partitioning_guided_multi_select]]
| |
| |headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
| |
| | |
| {{anchor|storage-interfaces}}
| |
| ==== Storage interfaces ====
| |
| The installer must be able to complete an installation using any supported locally connected storage interface.
| |
| {{hidden|header=What are they?|content='Locally connected storage interfaces' include PATA, SATA and SCSI.|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
| |
| {{hidden|header=References|content=
| |
| Test cases:
| |
| * [[QA:Testcase_install_to_SATA]]
| |
| * [[QA:Testcase_install_to_PATA]]
| |
| * [[QA:Testcase_install_to_SCSI]]
| |
| * [[QA:Testcase_install_to_SAS]]
| |
| |headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
| |
| | |
| {{anchor|disk-layouts}}
| |
| ==== Disk layouts ====
| |
| The installer must be able to complete an installation to a single disk using automatic partitioning.
| |
| {{hidden|header=Details!|content=...well, so long as the disk is big enough, of course. It must work whether the disk is formatted or not and whether or not it contains any existing data - but since this is an Alpha, it's OK if it can only install to a disk with existing data by overwriting it.|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
| |
| {{hidden|header=References|content=
| |
| * Proposed [https://lists.fedoraproject.org/pipermail/test/2012-October/110494.html 2012-10-01], implemented [https://lists.fedoraproject.org/pipermail/test/2012-October/110531.html 2012-10-02].
| |
| * Test case: [[QA:Testcase_partitioning_guided_empty]]
| |
| |headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
| |
| | |
| {{anchor|scripted-user-creation}}
| |
| ==== Scripted user creation ====
| |
| The scripted installation mechanism must provide a working function for creating local user accounts, including the ability to specify a hashed password, and for specifying a hashed password for the root account.
| |
| {{hidden|header=References|content=
| |
| * Part of Fedora 21 Server release criteria drafts, [added https://lists.fedoraproject.org/pipermail/server/2014-June/001294.html] 2014-06-26
| |
| * Test case: [[QA:Testcase_kickstart_user_creation]]
| |
| |headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
| |
| | |
| {{anchor|rescue-mode}}
| |
| | |
| ==== Rescue mode ====
| |
| The rescue mode of the installer must start successfully and be able to detect and mount an existing default installation.
| |
| {{hidden|header=Start successfully?|content='Start successfully' means it should be able to get you to a console that can interact with the mounted installation.|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
| |
| {{hidden|header=References|content=Test case: [[QA:Testcase_Anaconda_rescue_mode]]|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
| |
| | |
| {{anchor|update-image}}
| |
| ==== Update image ====
| |
| The installer must be able to download and use an [[Anaconda/Updates|installer update image]] from an HTTP server.
| |
| {{hidden|header=References|content=
| |
| * Proposed [https://lists.fedoraproject.org/pipermail/test/2012-January/105261.html 2012-01-30], implemented [https://lists.fedoraproject.org/pipermail/test/2012-February/105676.html 2012-02-20].
| |
| * Test case: [[QA:Testcase_Anaconda_updates.img_via_URL]]
| |
| |headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
| |
| | |
| {{anchor|failure-reporting}}
| |
| ==== Failure reporting ====
| |
| The installer must be able to report failures to Bugzilla, with appropriate information included.
| |
| {{hidden|header=You mean, ANY failures?|content=No, silly - we mean crashes, really. This is about the crash reporting capabilities: when the installer crashes, it should pop up some dialogs that let you send a report containing data on the crash.|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
| |
| {{hidden|header=References|content=Test case: [[QA:Testcase_Anaconda_save_traceback_to_bugzilla]]|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
| |
| | |
| {{anchor|post-install-requirements}}
| |
| === <span style="text-decoration:underline">Post-install requirements</span> ===
| |
| Except where otherwise specified, each of these requirements applies to all supported configurations described [[#initialization-requirements|above]]. These requirements are not applicable to [[Cloud]] images.
| |
| | |
| {{anchor|expected-installed-system-boot-behavior}}
| |
| ==== Expected installed system boot behavior ====
| |
| * A working mechanism to create a user account must be clearly presented during installation and/or first boot of the installed system.
| |
| * A system installed with a release-blocking desktop must boot to a log in screen where it is possible to log in to a working desktop using a user account created during installation or a 'first boot' utility.
| |
| * A system installed without a graphical package set must boot to a state where it is possible to log in through at least one of the default virtual consoles.
| |
| {{hidden|header=Encrypted partitions|content=In all of the above cases, if any system partitions were encrypted as part of the installation, the boot process must prompt for the passphrase(s) and correctly unlock the partition(s) when provided with the correct passphrase(s).|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
| |
| {{hidden|header=User intervention|content=In all of the above cases, the boot should proceed without any unexpected user intervention being required. On a graphical install, if the user explicitly intervenes to prevent graphical boot by passing a bootloader parameter, the non-graphical requirement comes into effect.|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
| |
| {{hidden|header=System-specific bugs|content=System-specific bugs don't necessarily constitute an infringement of this criterion - for instance, if the system fails to boot because of a bug in the support some specific system's hardware, that is unlikely to constitute a violation unless the system is an extremely popular one. See [[Blocker_Bug_FAQ]] for more discussion of this.|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
| |
| {{hidden|header=Use for severe issues in applying updates|content=These criteria can be used to cover known severe issues in applying post-release updates. For instance, if there was a bug that meant the system would install and boot fine but would break as soon as the user ran 'yum update', that may well be covered by these criteria.|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
| |
| {{hidden|header=First boot utilities|content=On the first boot after installation, a utility for creating user accounts and other configuration may (''may'', not ''must'') run prior to a log in screen appearing.|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
| |
| {{hidden|header=References|content=
| |
| * Requirement for graphical installs to boot to desktop was in original Fedora 13 criteria revision.
| |
| * Changes to cover non-graphical installs were proposed [https://lists.fedoraproject.org/pipermail/test/2010-August/092615.html 2010-08-12], implemented [https://lists.fedoraproject.org/pipermail/test/2010-August/092784.html 2010-08-16].
| |
| * Changes to cover firstboot were proposed [https://lists.fedoraproject.org/pipermail/test/2011-March/097859.html 2011-03-17], implemented [https://lists.fedoraproject.org/pipermail/test/2011-March/098365.html 2011-03-29].
| |
| * Change to stop requiring text mode firstboot to work was proposed [https://lists.fedoraproject.org/pipermail/test/2011-August/101727.html 2011-08-08], implemented [https://lists.fedoraproject.org/pipermail/test/2011-August/101916.html 2011-08-17].
| |
| * Wording was simplified and clarified as part of the major Fedora 19 criteria revision.
| |
| * Change to reflect F19 firstboot->initial-setup/gnome-initial-setup migration and anaconda user creation [https://lists.fedoraproject.org/pipermail/test/2013-July/117053.html proposed 2013-07-18], [https://lists.fedoraproject.org/pipermail/test/2013-July/117132.html implemented 2013-07-24].
| |
| * Test cases:
| |
| ** [[QA:Testcase_Anaconda_user_creation]]
| |
| ** [[QA:Testcase_base_initial_setup]]
| |
| ** [[QA:Testcase_base_startup]]
| |
| |headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
| |
| | |
| {{anchor|system-service-manipulation}}
| |
| ==== System service manipulation ====
| |
| The default system init daemon (e.g. systemd) must be capable of starting, stopping, enabling and disabling correctly-defined services.
| |
| {{hidden|header="Correctly-defined services"|content=This criterion is not intended to require there are no broken services in the distribution, but that the init daemon itself works. The criterion is not violated
| |
| by a buggy service script, only if the init daemon itself is broken. A sufficiently-important service being broken might constitute a violation of another criterion - for instance, a service for a logging daemon being broken might violate the requirement that logging works - but not this one.|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
| |
| {{hidden|header=References|content=
| |
| * Proposed [https://lists.fedoraproject.org/pipermail/test/2014-July/121862.html 2014-07-04], revised proposal [https://lists.fedoraproject.org/pipermail/test/2014-July/121879.html 2014-07-07]
| |
| * Test case: [[QA:Testcase_base_service_manipulation]]
| |
| |headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
| |
| | |
| {{anchor|updates}}
| |
| ==== Updates ====
| |
| The installed system must be able to download and install updates with the default console package manager.
| |
| {{hidden|header=Bugs in particular updates|content=A bug in some particular update package will not usually constitute a violation of this criterion. It's really about the update mechanism functioning correctly. So if yum is working fine, but the update transaction fails because there happen to be two conflicting packages in the repositories, that's not a release blocking problem.|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
| |
| {{hidden|header=References|content=
| |
| * Requirement was in force for 'default desktop' in original Fedora 13 criteria revision.
| |
| * Modification to cover 'release-blocking desktops' was proposed [https://lists.fedoraproject.org/pipermail/test/2011-May/100183.html 2011-05-17], implemented [https://lists.fedoraproject.org/pipermail/test/2011-May/100646.html 2011-05-31].
| |
| * Modification to move graphical update requirement to Beta or Final agreed during [http://meetbot.fedoraproject.org/fedora-blocker-review/2013-09-18/ 2013-09-18 blocker review meeting].
| |
| * Test case: [[QA:Testcase_desktop_updates]]
| |
| |headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
| |
| | |
| {{anchor|system-logging}}
| |
| ==== System logging ====
| |
| A system logging infrastructure must be available, enabled by default, and working.
| |
| {{hidden|header=What do you mean, 'working'?|content=Well, 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 Fedora Project.|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
| |
| {{hidden|header=References|content=
| |
| * Thread [https://lists.fedoraproject.org/pipermail/test/2011-May/100088.html 'Syslog not running' 2011-05-16].
| |
| * Proposed [https://lists.fedoraproject.org/pipermail/test/2011-May/100126.html 2011-05-16], implemented 2011-05-17 as part of initial Fedora 16 Alpha criteria page creation.
| |
| * Test case: [[QA:Testcase_base_system_logging]]
| |
| |headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
| |
| | |
| {{anchor|selinux-configuration}}
| |
| ==== SELinux configuration ====
| |
| Unless explicitly specified otherwise, after system installation SELinux must be enabled and in enforcing mode.
| |
| {{hidden|header=References|content=
| |
| * Part of [https://lists.fedoraproject.org/pipermail/server/2014-June/001198.html initial Server release criteria proposal], 2014-06-06
| |
| * In fact applies to all products, so moved to generic criteria as part of combined Fedora 21 Alpha criteria draft, 2014-07-07
| |
| * Test case: [[QA:Testcase_base_selinux]]
| |
| |headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
| |
| | |
| {{anchor|shutdown}}
| |
| ==== Shutdown ====
| |
| It must be possible to trigger a clean system shutdown using standard console commands.
| |
| {{hidden|header=What do you mean, 'clean'?|content=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.|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
| |
| {{hidden|header=References|content=
| |
| * Proposed [https://lists.fedoraproject.org/pipermail/test/2011-July/101446.html 2011-07-22], Implemented [https://lists.fedoraproject.org/pipermail/test/2011-July/101518.html 2011-07-27].
| |
| * Test case: [[QA:Testcase_desktop_login]]
| |
| |headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
| |
| | |
| {{anchor|self-identification}}
| |
| ==== Self-identification ====
| |
| Any component which prominently identifies a Fedora release version number, code name or milestone (Alpha, Beta, Final) must do so correctly.
| |
| {{hidden|header=References|content=
| |
| * Initial artwork criteria proposed [https://lists.fedoraproject.org/pipermail/test/2010-September/093476.html 2010-10-10], implemented [https://lists.fedoraproject.org/pipermail/test/2010-September/093568.html 2010-10-13].
| |
| * Revision to be less strict and pervasive proposed [https://lists.fedoraproject.org/pipermail/test/2012-August/109712.html 2012-08-28], implemented [https://lists.fedoraproject.org/pipermail/test/2012-September/109818.html 2012-09-04].
| |
| * Test case: [[QA:Testcase_base_startup]]
| |
| |headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
| |
| | |
| {{anchor|required-applications}}
| |
| ==== Required applications ====
| |
| It must be possible to run the default web browser and a terminal application from all release-blocking desktop environments.
| |
| {{hidden|header=Web browser requirements|content=The web browser must be able to download files, load extensions (if applicable), and log into [https://admin.fedoraproject.org/accounts/ FAS].|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
| |
| {{hidden|header=References|content=
| |
| * Requirement was in force for 'default desktop' in original Fedora 13 criteria revision.
| |
| * Modification to cover 'release-blocking desktops' was proposed [https://lists.fedoraproject.org/pipermail/test/2011-May/100183.html 2011-05-17], implemented [https://lists.fedoraproject.org/pipermail/test/2011-May/100646.html 2011-05-31].
| |
| * Test cases: [[QA:Testcase_desktop_browser]], [[QA:Testcase_desktop_terminal]]
| |
| |headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
| |
| | |
| {{anchor|desktop-background}}
| |
| ==== Desktop background ====
| |
| The default desktop background must be different from that of the two previous stable releases.
| |
| {{hidden|header=References|content=
| |
| * Initial artwork criteria proposed [https://lists.fedoraproject.org/pipermail/test/2010-September/093476.html 2010-10-10], implemented [https://lists.fedoraproject.org/pipermail/test/2010-September/093568.html 2010-10-13].
| |
| * Revision to be less strict and pervasive proposed [https://lists.fedoraproject.org/pipermail/test/2012-August/109712.html 2012-08-28], implemented [https://lists.fedoraproject.org/pipermail/test/2012-September/109818.html 2012-09-04].
| |
| * Test case: [[QA:Testcase_base_startup]]
| |
| |headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
| |
| | |
| {{anchor|server-product-requirements}}
| |
| === <span style="text-decoration:underline">[[Server]] Product requirements</span> ===
| |
| These requirements apply only to the Server product.
| |
| | |
| {{anchor|remote-authentication}}
| |
| ==== Remote authentication ====
| |
| It must be possible to join the system to a FreeIPA or Active Directory domain at install time and post-install, and the system must respect the identity, authentication and access control configuration provided by the domain.
| |
| {{hidden|header=Non-interactive only OK|content=The install-time capability is not required to be interactive (i.e. it is acceptable for it to be possible by kickstart only).|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
| |
| {{hidden|header=No local account requirement|content=This criterion is understood to mandate that there must be no requirement for a local user account to be created during install or first boot of a Server system.|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
| |
| {{hidden|header=References|content=
| |
| * Part of [https://lists.fedoraproject.org/pipermail/server/2014-June/001198.html initial Server release criteria proposal], 2014-06-06
| |
| * Test cases:
| |
| ** [[QA:Testcase_FreeIPA_realmd_join]]
| |
| ** [[QA:Testcase_realmd_join_kickstart]]
| |
| ** [[QA:Testcase_realmd_join_server]]
| |
| |headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
| |
| | |
| {{anchor|firewall-configuration}}
| |
| | |
| ==== Firewall configuration ====
| |
| After system installation without explicit firewall configuration, the system firewall must be active on all non-loopback interfaces. The only ports which may be open to incoming traffic are port 22 (ssh), port XX (Cockpit web interface), and any ports associated with server Roles selected during installation. Supported install-time firewall configuration options must work correctly.
| |
| {{hidden|header=Install time configuration|content=To explain the last part of this criterion - it is possible to include firewall configuration options in a kickstart-driven installation, and the criterion requires that those options work as expected. The options considered to be 'supported' are those documented at [[Anaconda/Kickstart#firewall]]. The case of a conflict between role-specified and manually-specified firewall configuration is not considered to be covered by these criteria.|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
| |
| {{hidden|header=References|content=
| |
| * Part of [https://lists.fedoraproject.org/pipermail/server/2014-June/001198.html initial Server release criteria proposal], 2014-06-06
| |
| * Test cases:
| |
| ** [[QA:Testcase_Server_firewall_default]]
| |
| ** [[QA:Testcase_kickstart_firewall]]
| |
| |headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
| |
| | |
| {{anchor|cockpit-management-interface}}
| |
| | |
| ==== Cockpit management interface ====
| |
| Unless explicitly specified otherwise, after system installation the Cockpit web management interface must be running and accessible on its default port (XX).
| |
| {{hidden|header=References|content=
| |
| * Part of [https://lists.fedoraproject.org/pipermail/server/2014-June/001198.html initial Server release criteria proposal], 2014-06-06
| |
| * Test case: [[QA:Testcase_Server_cockpit_default]]
| |
| |headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
| |
| | |
| <!--
| |
| 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}}
| |
| </span>
| |
| | |
| == 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 21 Beta Release Criteria]]
| |
| * [[Fedora 21 Final Release Criteria]]
| |
| * [[Blocker Bug FAQ]]
| |
| * [[QA:SOP blocker_bug process]]
| |
| * [[QA:SOP blocker_bug process#Automatic_blockers|Automatic blockers]]
| |
| * [[Packaging:Guidelines]]
| |
| | |
| [[Category:Release Criteria]]
| |
