Change deadlines

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(Some formatting help?)
(nth -> freeze exception)
(11 intermediate revisions by 6 users not shown)
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 tree are suspended until the release candidate is accepted.
+
At the change deadline, ''pushes'' to the branched development repository 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.''
+
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 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'''.   
+
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>.   
  
Refer to a picture of this process here: '''fixme'''
+
== Alpha and Beta public releases ==
  
== Alpha & Beta Public Releases ==
+
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 staging has started to the mirrors.
  
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 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.
; 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?
 
; Where should other changes be pushed?
: Pushes may continue to the ''updates-testing'' tree.
+
: Pushes may continue to the ''updates-testing'' repository.
 +
 
 +
== Final public release ==
  
== Final Release ==
+
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 [[QA:SOP_blocker_bug_process|accepted blocker bugs]] and [[QA:SOP_freeze_exception_bug_process|accepted freeze exception bugs]].
  
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'' 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>.
  
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'''.
+
[[Category:Release Engineering SOPs]]

Revision as of 01:41, 23 January 2013

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 21 is /pub/fedora/linux/development/21.

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/21), are suspended until the Release Candidate has been successfully tested and staging has started 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/21). The only exceptions are accepted blocker bugs and accepted freeze exception 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 21 is /pub/fedora/linux/updates/21.