No edit summary |
(Use consistant wording.) |
||
| Line 5: | Line 5: | ||
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.'' | 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 | The ''branched development'' repository 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 development repository path for {{FedoraVersion|long|next}} is <code>/pub/fedora/linux/development/{{FedoraVersion|number|next}}</code>. | ||
== Alpha and Beta public releases == | == Alpha and Beta public releases == | ||
| Line 11: | Line 11: | ||
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. | 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 | ; What can be pushed into the branched development repository? | ||
: Only blocker bugs of a public release (critical path or not) can be pushed to a | : Only blocker bugs of a public release (critical path or not) can be pushed to a ''branched development'' repository during this interim period, until the Release Candidate is ready to stage to mirrors. | ||
; Where should other changes be pushed? | ; Where should other changes be pushed? | ||
Revision as of 21:15, 7 September 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 branched development repository is the repository of packages that were originally branched from rawhide or have been updated through the Bodhi process. For example, the branched development repository path for Fedora 42 is /pub/fedora/linux/development/42.
Alpha and Beta public releases
At the change deadlines for Alpha and Beta, pushes to the branched development repository (e.g. /pub/fedora/linux/development/42), are suspended until the Release Candidate has been successfully tested and is being staged to the mirrors.
- What can be pushed into the branched development repository?
- Only blocker bugs of a public release (critical path or not) can be pushed to a branched development repository 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 public 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/42). 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 42 is /pub/fedora/linux/updates/42.