Editable copy of James Laskas PPC Release Criteria draft Contents [hide]
1 Alpha PowerPC Objectives 2 Alpha PowerPC Release Requirements 3 Alpha PowerPC Blocker Bugs 4 Contingency Plan 5 Confirming Alpha Requirements 6 Related Pages
 Alpha PowerPC Objectives
The objectives of the Alpha PowerPC release are to:
Publicly release installable media versions of a feature complete test release for Architectures/PowerPC shortly following the primary architecture release date Test accepted features of Fedora 16 Identify as many f16Betappc blocker bugs as possible Identify as many f16Blockerppc blocker bugs as possible
Alpha Release Requirements
In order to be released to the general public, the Alpha Candidate (RC) 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 the x86 architectures is GNOME and KDE, and for the ARM architectures is Xfce. 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 primary Products - Server, Workstation and Cloud - in their product requirement documents and/or technical specifications, and the KDE live image. As of Fedora 24, no 32-bit x86 image can be 'release-blocking', by FESCo policy. The canonical list of release-blocking images for Fedora 25 is on this page.
|1||All bugs blocking the Alpha tracker must be CLOSED||Incomplete (pknirsch)||pknirsch followup with bcl about parted blocker|
|2||There must be no file conflicts (cases where the files in some packages conflict but the packages have explicit Conflicts: tags are acceptable) or unresolved package dependencies during a media-based (DVD) install||Baude testing|
|3|| Where platform support exists, all dedicated installer images (except
||Not applicable (pknirsch)||PPC doesn't have a graphical boot menu|
|4||The installer must boot (if appropriate) and run on all primary architectures from default live image (if appropriate), DVD, and boot.iso install media||Needs clarification, too broad for Alpha|
|5||The boot menu for all installation 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 and attempting to use the generic driver||Needs verification||Kick testing|
|6||The installer must be able to use at least one of the HTTP or FTP remote package source options||Complete (Baude)||http/nfs tested|
|7||When booting from a DVD ISO image, the installer must be able to use the DVD local package source options||Complete (Baude)||Bug 743728 no longer an issue|
|8||The installer must be able to complete an installation using the text, graphical and VNC installation interfaces||Complete (hamzy)|
|9||The installer must be able to complete package installation with the default package set for each supported installation method||Baude/hamzy testing|
|10||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||Baude/hamzy testing|
|11||The installer must be able to complete an installation using the entire disk, existing free space, or existing Linux partitions methods, with or without encryption enabled||Install worked, but reboot later didn't allow entering the PW for encrypted FS. BZ will follow (baude)||Baude/hamzy testing|
|12||The rescue mode of the installer must start successfully and be able to detect and mount an existing default installation||Complete (baude)|
|13||The installer must be able to report failures to Bugzilla, with appropriate information included||Kick testing|
|14||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. 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||Works with unencrypted FS, otherwise same failure as #11||Kick testing|
|15||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||Works with unencrypted FS but fails to start Gnome, see #17, otherwise same failure as #11||Kick testing|
|16||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||Complete (baude)|
|17||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 FAS||Gnome broken, incomplete, bz will follow|
|18||The installed system must be able to download and install updates with yum and the default graphical package manager in all release-blocking desktops||Gnome broken, incomplete due to graphical package manager, bz will follow, but yum works|
|19||The default Fedora artwork must either refer to the current Fedora release under development (Fedora 16), or reference an interim release milestone (e.g. Alpha or Beta). If a release version number is used, it must match the current Fedora release under development. This includes artwork used in the installer, graphical bootloader menu, firstboot, graphical boot, graphical login and desktop background.||Complete up to graphical login not testable due to broken Gnome|
|20||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||Complete (baude)|
Alpha Blocker Bugs
A bug is considered a Alpha 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 Alpha test plans or dramatically reduces test coverage
- Bug relates to an unmet Alpha 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.