Zen

Source string Source string

82/10000 · 82

The string is read only.

English Actions
Process for promoting a Fedora deliverable to Edition
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.
What makes an "Edition"?
A Fedora Edition:
addresses a sufficiently distinct, relevant, and broad use-case or user-base 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 Four Foundations.
Prerequisites
The candidate Edition must be backed by a team that holds regular public meetings.
The candidate Edition must get trademark approval from the {team_name}. 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) (link:{FWIKI}/Workstation/Workstation_PRD[example]). The PRD is used by other teams within Fedora. For example, the Quality Team uses it to develop release criteria and test cases and the Marketing Team uses it to develop collateral and positioning. The PRD must include:
Market target, including key use cases and personas.
Core services and features.
Core applications.
Unique policies for installation, updates, etc.
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 (link:{FWIKI}/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.
Process
When all of the prerequisites have been met and approved by the {team_name}, 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 {team_name}*.
File a ticket and participate in related discussion.
*Review test cases and release criteria with the Quality Team*.
The Quality 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 Quality Team.

Loading…

User avatar None

String updated in the repository
The candidate Edition must be backed by a team that holds regular public meetings.
The candidate Edition must be backed by a team that holds regular public meetings.
a year ago
Browse all string changes

Things to check

Multiple failing checks

Following checks are failing:
Mismatched full stop: Swedish, Turkish

Reset

Glossary

English English
No related strings found in the glossary.

String information

Source string description
type: Plain text
Flags
read-only
Source string location
./pages/policy/edition-promotion-policy.adoc:25
String age
a year ago
Last updated
a year ago
Source string age
a year ago
Translation file
pot/master/pages/policy/edition-promotion-policy.pot, string 10