giftpack.blogg.se

1. #FEDORA 23 WORKSTATION SYSTEM REQUIREMENTS INSTALL#
2. #FEDORA 23 WORKSTATION SYSTEM REQUIREMENTS UPDATE#
3. #FEDORA 23 WORKSTATION SYSTEM REQUIREMENTS PASSWORD#

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. The Change process is separate from this process. Bug relates to an unmet Final Release RequirementĪ Fedora Change being incomplete, in and of itself, does not constitute a blocker bug.Bug hinders execution of required Final test plans or dramatically reduces test coverage.Has a severity rating of high or greater and no reasonable workaround (see definition of severity and priority).

#FEDORA 23 WORKSTATION SYSTEM REQUIREMENTS UPDATE#

Cannot be fixed with a future stable update.Test cases: see each role's requirements page.Ī bug is considered a Final blocker bug if any of the following criteria are met:.

#FEDORA 23 WORKSTATION SYSTEM REQUIREMENTS INSTALL#

Validation of install media must work correctly for all release-blocking images. The canonical list of release-blocking images for Fedora 39 is on this page.Īll Fedora 23 Beta Release Criteria must be met.Īll bugs blocking the Final tracker must be CLOSED. The current set of release-blocking images includes the images defined by the three Editions - Server, Workstation and IoT - in their product requirement documents and/or technical specifications, the Everything network install image, key Cloud images, and the KDE live image. The term release-blocking images means all the images in which bugs are currently considered capable of blocking a Fedora release. 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 current set of release-blocking desktops for x86_64 is GNOME and KDE, and for aarch64 is GNOME. The term release-blocking desktops means all the desktop environments in which bugs are currently considered capable of blocking a Fedora 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. 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.

#FEDORA 23 WORKSTATION SYSTEM REQUIREMENTS PASSWORD#

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. Optional and nice to have items should not be included in this list. Mostly met items are incomplete until they are met. This is intended to make the decision process as clear and straightforward as possible. In order to be released to the general public, a compose must meet all of the following criteria.