View source for F19AlphaPPC checklist

== Alpha Objectives ==
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}}PPCBeta&hide_resolved=1 {{FedoraVersion|short|19}} PPC Beta blocker bugs] as possible
# Identify as many [https://bugzilla.redhat.com/showdependencytree.cgi?id={{FedoraVersion|short|19}}PPCFinal&hide_resolved=1 {{FedoraVersion|short|19}} PPC Blocker blocker bugs] as possible

== Alpha Release Requirements ==
{{Template:Release_criteria_preamble|prerelease=Alpha}}

=== <span style="text-decoration:underline">Process requirements</span> ===
{{Template:Release_criteria_preamble|prerelease=Alpha}}

{|
! Number !! Requirements !! Owner !! Status !! Comments
|-
!colspan="5"| Process requirements
|-
{{anchor|alpha-blockers-closed}}
| 1 || All bugs blocking the [https://bugzilla.redhat.com/showdependencytree.cgi?id=F19PPCAlpha&hide_resolved=1 Alpha tracker] must be [[BugZappers/BugStatusWorkFlow#CLOSED|CLOSED]] || PPC team || {{result|none}} ||
|-
{{anchor|correct-checksums}}
| 2 || 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}}
|| dwa || {{result|none}} ||
|-
{{anchor|no-broken-packages}}
| 3 || 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}}
|| dwa || {{result|none}} ||
|-
{{anchor|initialization-requirements}}
!colspan="5"| Initialization requirements
|-
{{anchor|release-blocking-images-must-boot}}
| 4 || All release-blocking images must boot in their supported configurations.
{{hidden|header=Supported architectures|content=Supported architectures are PPC64 and Power7.|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
{{hidden|header=Supported media types|content=Release-blocking dedicated installer images must boot when written to optical or virtual media of an appropriate size (if applicable).|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_Methods_Boot_Iso]]
* [[QA:Testcase_Boot_Methods_Dvd]]
|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
|| || {{result|none}} ||
|-
{{anchor|expected-image-boot-behavior}}
| 5 || Release-blocking dedicated installer images must boot to the expected boot menu, and then after a reasonable timeout to the installer. 
{{hidden|header=Boot menu contents|content=The boot menu for all supported installer 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}}
|| Kick_ || {{result|pass|Kick_}} || yaboot timeout is intentionally set very high
|-
{{anchor|installer-requirements}}
!colspan="5"|Installer requirements
Except where otherwise specified, each of these requirements applies to all supported configurations described [[#initialization-requirements|above]].
|-
{{anchor|installer-must-run}}
| 6 || 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.|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}}
|| || {{result|none}} ||
|-
{{anchor|remote-package-sources}}
| 7 || 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}}
|| gustavold / IBM || {{result|none}} ||
|-
{{anchor|dvd-package-source}}
| 8 || When using the DVD image, the installer must be able to use the DVD as a package source.
{{hidden|header=References|content=Test case: [[QA:Testcase_install_repository_DVD_default]]|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
|| gustavold / IBM || {{result|pass|gustavold}} ||
|-
{{anchor|installer-interfaces}}
| 9 || When using the dedicated installer images, the installer must be able to complete an installation using the text 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_Text]]
* [[QA:Testcase_Anaconda_User_Interface_VNC]]
* [[QA:Testcase_Anaconda_User_Interface_VNC_Vncconnect]]
|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
|| gustavold / IBM || {{result|none}} ||
|-
{{anchor|package-sets}}
| 10 || 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=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]]
|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
|| gustavold / IBM || {{result|warn|gustavold}} || gnome crashes on startup, kde works fine.
|-
{{anchor|disk-selection}}
| 11 || 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: FIXME
|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
|| gustavold / IBM || {{result|pass|gustavold}} ||
|-
{{anchor|storage-interfaces}}
| 12 || 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_device]]
* [[QA:Testcase_install_to_PATA_device]]
* [[QA:Testcase_install_to_SCSI_device]]
|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
|| gustavold / IBM || {{result|none}} ||
|-
{{anchor|disk-layouts}}
| 13 || 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_Anaconda_autopart_install]]
|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
|| gustavold / IBM || {{result|pass|gustavold}} ||
|-
{{anchor|rescue-mode}}
| 14 || 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}}
|| gustavold / IBM || {{result|none}} ||
|-
{{anchor|update-image}}
| 15 || 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}}
|| gustavold / IBM || {{result|none}} ||
|-
{{anchor|failure-reporting}}
| 16 || 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}}
|| gustavold / IBM || {{result|none}} ||
|-
{{anchor|post-install-requirements}}
!colspan="5"|Post-install requirements
Except where otherwise specified, each of these requirements applies to all supported configurations described [[#initialization-requirements|above]].
|-
{{anchor|expected-installed-system-boot-behavior}}
| 17 || * A system installed with a graphical package set must boot to the 'firstboot' utility on the first boot after installation. The firstboot utility must be able to create a working user account.
* After firstboot is completed and on subsequent boots, a graphical install must boot to a log in screen where it is possible to log in to a working desktop as the user created during firstboot.
* 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=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.
* Test cases: [[QA:Testcase_base_firstboot]], [[QA:Testcase_base_startup]]
|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
|| Kick_ || {{result|warn|Kick_|951013}} || Reusing existing partitions not possible, the rest works
|-
{{anchor|required-applications}}
| 18 || 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 case: [[QA:Testcase_desktop_browser]]
|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
|| Kick_ || {{result|pass|Kick_}} || Tested Firefox in KDE, works!
|-
{{anchor|updates}}
| 19 || The installed system must be able to download and install updates with yum and with the default graphical package manager in all release-blocking desktops.
{{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 mechanisms 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].
* Test case: [[QA:Testcase_desktop_updates]]
|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
|| Kick_ || {{result|warn|Kick_|928859}} || Gnome Desktop could not be tested
|-
{{anchor|desktop-background}}
| 20 || 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}}
|| Kick_ || {{result|none}} ||
|-
{{anchor|self-identification}}
| 21 || 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}}
|| pknirsch || {{result|none}} ||
|-
{{anchor|system-logging}}
| 22 || 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}}
|| pknirsch || {{result|pass|pknirsch}} ||
|-
{{anchor|shutdown}}
| 23 || 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}}
|| pknirsch || {{result|pass|pknirsch}} ||
|-
|}
<references />

{{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]]