(Add link) |
(Some formatting help?) |
||
| Line 5: | Line 5: | ||
A ''push'' is a a release engineering term for moving a package into a particular tree or repo 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 a release engineering term for moving a package into a particular tree or repo 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 release tree or yum repo 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, in Fedora 14 the name of the branched tree is | The ''stable branch'' is the release tree or yum repo 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, in Fedora 14 the name of the branched tree is '''pub/fedora/linux/development/14'''. | ||
Refer to a picture of this process here: '''fixme''' | |||
== Alpha & Beta Public Releases == | == Alpha & Beta Public Releases == | ||
At the change deadlines for Alpha and Beta, pushes to the ''branched development'' tree, for example | At the change deadlines for Alpha and Beta, pushes to the ''branched development'' tree, for example '''pub/fedora/linux/development/14''', are suspended until the Release Candidate has been successfully tested and is being staged to the mirrors. | ||
Only blocker bugs of a public release (critical path or not) can be pushed to a stable branch during this interim period. | ; 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. | |||
Pushes may continue to the ''updates-testing'' tree | ; Where should other changes be pushed? | ||
: Pushes may continue to the ''updates-testing'' tree. | |||
== Final Release == | == Final Release == | ||
After the change deadlines for the Final release no more updates are made to the ''branched development'' tree, for example | After the change deadlines for the Final release no more updates are made to the ''branched development'' tree, for example '''pub/fedora/linux/development/14'''. The only exceptions are ''accepted blocker bugs.'' | ||
All updates | All updates after this time are considered ''zero day updates'' of the release, and are pushed to the ''updates'' repo which is available on the public availability date. For example, for Fedora 14 this repo is '''pub/fedora/linux/updates/14'''. | ||
Revision as of 23:46, 3 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 tree are suspended until the release candidate is accepted.
A push is a a release engineering term for moving a package into a particular tree or repo 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 release tree or yum repo of packages that were originally branched from rawhide or have been updated through the Bodhi process. For example, in Fedora 14 the name of the branched tree is pub/fedora/linux/development/14.
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 tree, for example pub/fedora/linux/development/14, 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 tree.
Final Release
After the change deadlines for the Final release no more updates are made to the branched development tree, for example pub/fedora/linux/development/14. 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 repo which is available on the public availability date. For example, for Fedora 14 this repo is pub/fedora/linux/updates/14.