(Some formatting help?) |
(Minor wiki tweaks and reword. Add use of FedoraVersion template) |
||
| Line 1: | Line 1: | ||
Change deadlines happen two weeks before the public release of each Fedora Alpha, Beta, and Final release. | Change deadlines happen two weeks before the public release of each Fedora Alpha, Beta, and Final release. | ||
At the change deadline, ''pushes'' to the branched development | At the change deadline, ''pushes'' to the branched development repository are suspended until the release candidate is accepted. | ||
A ''push'' is | A ''push'' is a release engineering term for moving a package into a particular repository of packages. After a release has been branched, a new or updated package must receive testing feedback via Bodhi before it is allowed into the ''stable branch.'' | ||
The ''stable branch'' is the | The ''stable branch'' is the repository of packages that were originally branched from rawhide or have been [[Package_update_HOWTO#Working_with_packages_in_the_stable_branches|updated through the Bodhi process]]. For example, the branched repository path for {{FedoraVersion|long|next}} is <code>/pub/fedora/linux/development/{{FedoraVersion|number|next}}</code>. | ||
Refer to a picture of this process here: '''fixme''' | Refer to a picture of this process here: '''fixme''' | ||
| Line 11: | Line 11: | ||
== Alpha & Beta Public Releases == | == Alpha & Beta Public Releases == | ||
At the change deadlines for Alpha and Beta, pushes to the ''branched development'' | At the change deadlines for Alpha and Beta, pushes to the ''branched development'' repository (e.g. <code>/pub/fedora/linux/development/{{FedoraVersion|number|next}}</code>), are suspended until the Release Candidate has been successfully tested and is being staged to the mirrors. | ||
; What can be pushed into the stable branch? | ; What can be pushed into the stable branch? | ||
| Line 17: | Line 17: | ||
; Where should other changes be pushed? | ; Where should other changes be pushed? | ||
: Pushes may continue to the ''updates-testing'' | : Pushes may continue to the ''updates-testing'' repository. | ||
== Final Release == | == Final Release == | ||
After the change deadlines for the Final release no more updates are made to the ''branched development'' | After the change deadlines for the Final release no more updates are made to the ''branched development'' repository (e.g. <code>/pub/fedora/linux/development/{{FedoraVersion|number|next}}</code>). The only exceptions are ''accepted blocker bugs.'' | ||
All updates after this time are considered ''zero day updates'' of the release, and are pushed to the ''updates'' | All updates after this time are considered ''zero day updates'' of the release, and are pushed to the ''updates'' repository which is available on the public availability date. For example, the repository for {{FedoraVersion|long|next}} is <code>/pub/fedora/linux/updates/{{FedoraVersion|number|next}}</code>. | ||
Revision as of 12:44, 4 August 2010
Change deadlines happen two weeks before the public release of each Fedora Alpha, Beta, and Final release.
At the change deadline, pushes to the branched development repository are suspended until the release candidate is accepted.
A push is a release engineering term for moving a package into a particular repository of packages. After a release has been branched, a new or updated package must receive testing feedback via Bodhi before it is allowed into the stable branch.
The stable branch is the repository of packages that were originally branched from rawhide or have been updated through the Bodhi process. For example, the branched repository path for Fedora 41 is /pub/fedora/linux/development/41.
Refer to a picture of this process here: fixme
Alpha & Beta Public Releases
At the change deadlines for Alpha and Beta, pushes to the branched development repository (e.g. /pub/fedora/linux/development/41), are suspended until the Release Candidate has been successfully tested and is being staged to the mirrors.
- What can be pushed into the stable branch?
- Only blocker bugs of a public release (critical path or not) can be pushed to a stable branch during this interim period, until the Release Candidate is ready to stage to mirrors.
- Where should other changes be pushed?
- Pushes may continue to the updates-testing repository.
Final Release
After the change deadlines for the Final release no more updates are made to the branched development repository (e.g. /pub/fedora/linux/development/41). The only exceptions are accepted blocker bugs.
All updates after this time are considered zero day updates of the release, and are pushed to the updates repository which is available on the public availability date. For example, the repository for Fedora 41 is /pub/fedora/linux/updates/41.