|Fedora Editions are curated sets of packages, guidelines and configuration, and artifacts built from those pieces, that address a specific, targeted use-case. The Editions are the primary Fedora outputs that most Fedora users are encouraged to use and directed towards through the download site.|
|This document describes the process for promoting an existing Fedora deliverable to Edition status.|
|addresses a distinct, relevant, and broad use-case or userbase that a Fedora Edition is not currently serving;|
|is a long term investment for the Fedora Project; and|
|is consistent with all of Fedora's foundations.|
|The candidate Edition must be backed by a team that holds regular public meetings|
|The candidate Edition must get trademark approval from the Fedora Council. If this includes a name change or a new name (e.g. “Fedora Bilverslue”), plan time for legal review.|
|The candidate Edition must have a product requirements document (PRD) (https://fedoraproject.org/wiki/Workstation/Workstation_PRD[example]). The PRD is used by other teams within Fedora (for example: the QA team uses it to develop release criteria and test cases, the marketing team uses it to develop collateral and positioning). The PRD must include:|
|Scope of hardware support (including anything that is explicitly unsupported)|
|Produced deliverables, and whether or not they should be considered release blocking|
|The candidate Edition may have a technical specification (https://fedoraproject.org/wiki/Workstation/Technical_Specification[example]) that provides additional detail about the specific features described in the PRD.|
|It is helpful to have someone on the team assigned to handle the bureaucratic tasks|
|When all of the prerequisites have been met, and approved by the Fedora Council, the team submits promotion as a System-Wide Change. This ensures that Release Engineering, FESCo, and the community at large have the opportunity to provide input. It also implies that the promotion may be delayed to the next release if the appropriate supporting pieces are not in place by the Beta or GA freezes.|
|Prior to submitting the Change proposal, the following tasks should be completed:|
*Approval from the Council.*
File a ticket and participate in related discussion.
*Review test cases and release criteria with QA.*
The QA team will draft test cases and release criteria based on the PRD.
However, the Edition team must verify that these are valid.
The Edition team may choose to assign a person to be the liaison with the QA team.
*Work with Release Engineering.*
The Edition team should work with release engineering on how they are planning on composing the new edition, release process, mirrors sync locations, any changes needed to koji, bodhi or autosigning.
|After the change proposal is approved, the following additional tasks should be completed no later than the Beta freeze, which should be considered the contingency deadline for the change. Note that these tasks should be started as early as possible.|
*Request design deliverables.*
If customized graphics for the website, stickers, et cetera are needed, the Edition team should contact the Design team as soon as possible.
*Provide updated website content.*
The Edition team should send text, graphics, and screenshots to the Websites team as soon as possible to ensure getfedora.org will be up-to-date on release day.