Release criteria - gooseproject/main GitHub Wiki

Table of Contents Final Objectives Final Release Requirements Contingency Plan Confirming Final Requirements

The objective of the Final release is to:

1. Provide a polished final release suitable for meeting the needs of our Target Audience

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.

Release Requirements:

1. All bugs blocking the GoOSe 6.0 Release tracker must be CLOSED
2. 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.
3. If there is embedded checksum on ISO media, it must be correct.
4. The installer must be able to use all supported local and remote package source options
5. The installer must be able to complete an installation using network-attached storage devices (e.g. iSCSI, FCoE, Fibre Channel)
6. The installer must be able to complete an installation using all supported interfaces
7. 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
8. The installer must be able to use an installer update image retrieved from removable media, remote installation source and HTTP server
9. All services in a default install must start properly
10. All critical path actions on release-blocking desktop environments should correctly display all sufficiently complete translations available for use
11. Unless otherwise documented, there must be no SELinux 'AVC: denied' messages
12. All known bugs that can cause corruption of user data must be fixed or documented at Common GoOSe 6.0 bugs
13. Menu sanity - the following criteria refer to both a live image and default installed system, and to all release-blocking desktops
    • 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
    • All applications listed under the Applications menu or category must start successfully
    • 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
    • No application may unintentionally appear twice in the menus. In particular, items under System must not appear under Applications
14. All elements of the default panel (or equivalent) configuration in all release-blocking desktops must function correctly in common use
15. 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
16. No notices or alerts about pre-release status should be present
17. A spin-kickstarts 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
18. 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
19. A goose-release package containing the correct names, information and repository configuration for a final GoOSe release (as opposed to a pre-release) must be present on ISO media

• If all of the Final Release Requirements are not met by 02:00 UTC on Wednesday 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 weekly GoOSe meetings.

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 weekly GoOSe Meetings.