Fedora 17 Final Release Criteria

Final Objectives
The objective of the Final release is to:
 * 1) Provide a polished final release suitable for meeting the needs of our Target Audience

Final Release Requirements
Release Requirements:
 * 1) All Fedora 17 Beta Release Criteria must be met
 * 2) All bugs blocking the F17Blocker tracker must be CLOSED
 * 3) All release media must include a standalone memory test utility. A boot menu option to launch this utility must be present and must work correctly.
 * 4) If there is embedded checksum on ISO media, it must be correct.
 * 5) The installer must be able to use all supported local and remote package source options
 * 6) The installer must be able to complete an installation using any network-attached storage devices (e.g. iSCSI, FCoE, Fibre Channel)
 * 7) The installer must be able to complete an installation using all supported interfaces
 * 8) The installer must be able to create and install to any workable partition layout using any file system offered in a default installer configuration, LVM, software, hardware or BIOS RAID, or combination of the above
 * 9) The installer must be able to install into free space alongside an existing clean single-partition Windows installation and either install a bootloader which can boot into the Windows installation, or leave the Windows bootloader untouched and working
 * 10) The installer must be able to use an installer update image retrieved from removable media, remote installation source and HTTP server
 * 11) The release must boot successfully as Xen DomU with releases providing a functional, supported Xen Dom0 and widely used cloud providers utilizing Xen. This does not include any issues limited to the release functioning as Xen Dom0
 * 12) All services in a default install must start properly
 * 13) All critical path actions on release-blocking desktop environments should correctly display all sufficiently complete translations available for use
 * 14) In most cases, there must be no SELinux 'AVC: denied' messages or abrt crash notifications on initial boot and subsequent login (see Blocker_Bug_FAQ)
 * 15) All known bugs that can cause corruption of user data must be fixed or documented at Common F17 bugs
 * 16) Menu sanity - the following criteria refer to both a live image and default installed system, and to all release-blocking desktops
 * 17) * All Applications listed in the system menus (or equivalent) must have icons which have a consistent appearance and sufficiently high resolution to avoid appearing blurry
 * 18) * All applications listed under the Applications menu or category must start successfully
 * 19) * All applications listed under the Applications menu or category must withstand a basic functionality test and not crash after a few minutes of normal use. They must also have working Help and Help -> About menu items
 * 20) * No application may unintentionally appear twice in the menus. In particular, items under System must not appear under Applications
 * 21) All elements of the default panel (or equivalent) configuration in all release-blocking desktops must function correctly in common use
 * 22) Saving passwords in the desktop default keyring (if the desktop implements one), and retrieving passwords from the keyring, must work for all release-blocking desktops
 * 23) The proposed final Fedora artwork must be included and enabled by default for the installer, graphical boot, firstboot, graphical login and desktop background.  All Fedora artwork must be consistent with the proposed final theme, and if any artwork contains a graphical version number, the version number used must match the Fedora release number.  Generic release artwork (e.g. Alpha, Beta, Development) must not be used for the final release
 * 24) No notices or alerts about pre-release status should be present
 * 25) A  package which contains the exact kickstart files used to build the release must be present in the release repository. The included kickstarts must define the correct set of release repositories
 * 26) The final branded release notes from the Documentation team must be present on ISO media and the appropriately versioned generic release notes must be available in the online release repository
 * 27) A  package containing the correct names, information and repository configuration for a final Fedora release (as opposed to a pre-release) must be present on ISO media while the appropriately versioned  package must be available in the online release repository

Contingency Plan

 * If all of the Final Release Requirements are not met by 20:00 UTC on Tuesday the week prior to release day, the release will be delayed by one week so that the Final 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 Go/No-Go Meeting.

Confirming Final 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 Go/No-Go Meeting.

Related Pages

 * Fedora Release Criteria
 * Fedora 17 Alpha Release Criteria
 * Fedora 17 Beta Release Criteria
 * Blocker Bug FAQ
 * Packaging:Guidelines