User:Adamwill/Draft workstation release criteria

Alpha

Post-install requirements

Except where otherwise specified, each of these requirements applies to all supported configurations described above.

Expected installed system boot behavior

• A working mechanism to create a user account must be clearly presented during installation and/or first boot of the installed system.
• The system must boot to a log in screen where it is possible to log in to a working desktop using a user account created during installation or a 'first boot' utility.

Encrypted partitions

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).

User intervention

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.

System-specific bugs

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.

Use for severe issues in applying updates

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.

First boot utilities

On the first boot after installation, a utility for creating user accounts and other configuration may (may, not must) run prior to a log in screen appearing.

References

• Requirement for graphical installs to boot to desktop was in original Fedora 13 criteria revision.
• Changes to cover non-graphical installs were proposed 2010-08-12, implemented 2010-08-16.
• Changes to cover firstboot were proposed 2011-03-17, implemented 2011-03-29.
• Change to stop requiring text mode firstboot to work was proposed 2011-08-08, implemented 2011-08-17.
• Wording was simplified and clarified as part of the major Fedora 19 criteria revision.
• Change to reflect F19 firstboot->initial-setup/gnome-initial-setup migration and anaconda user creation proposed 2013-07-18, implemented 2013-07-24.
• Separated into per-Product variations as part of the Fedora.next Product split between Fedora 20 and Fedora 21, with only parts relevant to each Product included in each Product's criteria.
• Test cases:
  • QA:Testcase_Anaconda_user_creation
  • QA:Testcase_base_initial_setup
  • QA:Testcase_base_startup

Required applications

It must be possible to run the default web browser and a terminal application.

Web browser requirements

The web browser must be able to download files, load extensions (if applicable), and log into FAS.

References

• Requirement was in force for 'default desktop' in original Fedora 13 criteria revision.
• Modification to cover 'release-blocking desktops' was proposed 2011-05-17, implemented 2011-05-31.
• As part of Fedora.next product split revisions, Workstation-specific simplified variant created.
• Test cases: QA:Testcase_desktop_browser, QA:Testcase_desktop_terminal

Desktop background

The default desktop background must be different from that of the two previous stable releases.

References

• Initial artwork criteria proposed 2010-10-10, implemented 2010-10-13.
• Revision to be less strict and pervasive proposed 2012-08-28, implemented 2012-09-04.
• Copied unmodified to Workstation criteria as part of Fedora.next Product-based criteria split.
• Test case: QA:Testcase_base_startup