Final Objectives
The objective of the Final release is to:
- Provide a polished final release suitable for meeting the needs of our Target Audience
Final Release Requirements
In order to be released to the general public, the Final 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.
Release Requirements:
| Number | Requirements | Status | Comments |
|---|---|---|---|
| 1 | All F17BetaPPC checklist must be met | ||
| 2 | All bugs blocking the F17PPCBlocker 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 use an installer update image retrieved from removable media, remote installation source and HTTP server | ||
| 10 | All services in a default install must start properly | ||
| 11 | All critical path actions on release-blocking desktop environments should correctly display all sufficiently complete translations available for use | ||
| 12 | 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) | ||
| 13 | All known bugs that can cause corruption of user data must be fixed or documented at Common F17 bugs | ||
| 14 | All elements of the default Desktop panel (or equivalent) configuration in all release-blocking desktops must function correctly in common use | ||
| 15 | 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 | ||
| 16 | No notices or alerts about pre-release status should be present | ||
| 17 | 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 | ||
| 18 | A |
Final Blocker Bugs
A bug is considered a Final 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 Final test plans or dramatically reduces test coverage
- Bug relates to an unmet Final 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.
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.