From Fedora Project Wiki
.png){kind=small}
Information on this page is out of date
This page is no longer authoritative -- the Fedora Board decided in the Spring of 2011 to do away with this list of requirements, and now gives groups such as QA, Spins, Design, and Release Engineering the responsibility to set their own criteria for each new image produced. This page is being left here for the sake of reference.
This page is no longer authoritative -- the Fedora Board decided in the Spring of 2011 to do away with this list of requirements, and now gives groups such as QA, Spins, Design, and Release Engineering the responsibility to set their own criteria for each new image produced. This page is being left here for the sake of reference.
These are the requirements the Fedora Project places on any media created by the Project, intended to be handed out to end users by Ambassadors at events.
Requirements
Fit-and-Finish
Media artwork
- Media must have Fedora-themed artwork
- Artwork must clearly describe what is on the media. Example: "Fedora Desktop, i686 architecture"
Media sleeve artwork
- Sleve must have Fedora-themed artwork
- Artwork must clearly describe what is on the media. Example: "Fedora Desktop, i686 architecture"
- Artwork must clearly describe minimum system requirements
- Sleeve must have instructions on how to operate the disk. For example, the Desktop live media sleeve details how to install.
- If Fedora Design Team produced artwork is desired, this must be added to Fedora Design Team schedule by Alpha.
Boot Screens
- Boot screens must have Fedora-themed artwork, or no artwork at all
- Boot screens default selection must be the item we expect most users to choose, especially if they are new to Fedora
- Boot screens may layer in additional selections
Produced by Release Engineering
- ISO files are produced from packages in the Fedora repositories, by the Release Engineering team, using tools in Fedora
- The processes to produce the ISO must be documented in Fedora, and the tools may reside in the rel-eng git tree
- The above must be in place in sufficient time for Release Engineering to be able to perform the release
Quality Assurance
- Must have an approved test plan on file with the Fedora Quality Assurance team
- Test plan should be written involving members of the QA team
- Test plan must be executed by someone, with review by a member of the QA team. NB: this requires at least 2 people to participate in the testing.
- The above must be in place in sufficient time to allow testing, and remediation of uncovered issues, to occur
Corresponding Source Code Compliance
- The list of SRPMs used in the creation of the ISO image must be recorded in the correspondingsource git tree
Scheduling
- All proposed new media targets must be approved by Beta of the release for which they are relevant.
Non-Requirements
Hosting by Fedora Infrastructure
It has traditionally been our practice to host our media ISO images on Fedora Infrastructure servers, which include both http://alt.fedoraproject.org for "alternative" content such as Spins, and on the Fedora Mirror System. It is not a strict requirement that we do so, but it makes it easier for people to obtain an ISO that matches physical media.
Production of matching ISOs containing only SRPMs
By providing the list of SRPMs in the correspondingsource git tree, it is possible to create on an as-needed basis an ISO containing those SRPMs. This removes the need to produce and store an ISO image of these ahead of time.