Milestone freezes

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(Just a tweak and a question)
(Add Branch Freeze details as the current Branch Freeze process does not follow what we actually do)
(8 intermediate revisions by 5 users not shown)
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 ''stable branch'' '''[should this say ''branched development repository'' too? --[[User:Pfrields|pfrields]] 12:39, 5 August 2010 (UTC)]''' 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>.   
+
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>.   
 +
 
 +
== Bodhi usage policy ==
 +
From the Alpha Change Deadline up to the Final release, all updates to a ''branched development'' repository has to go through the Bodhi and update request has to be filled. Builds are submitted to updates-testing repository. When change deadline freeze is lifted (between Alpha/Beta release decision and Beta/Final Change Deadline freeze), tested updates with sufficient karma are pushed to stable repository. 
  
 
== Alpha and Beta public releases ==
 
== Alpha and 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 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 staging has started to the mirrors.
  
; What can be pushed into the stable branch?
+
; 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 stable branch during this interim period, until the Release Candidate is ready to stage to mirrors.
+
: 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?
Line 19: Line 22:
 
== Final public release ==
 
== Final public 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 ''accepted blocker bugs.''
+
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]].
  
 
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'' 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>.
 +
 +
[[Category:Release Engineering SOPs]]

Revision as of 11:26, 2 April 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 22 is /pub/fedora/linux/development/22.

Bodhi usage policy

From the Alpha Change Deadline up to the Final release, all updates to a branched development repository has to go through the Bodhi and update request has to be filled. Builds are submitted to updates-testing repository. When change deadline freeze is lifted (between Alpha/Beta release decision and Beta/Final Change Deadline freeze), tested updates with sufficient karma are pushed to stable repository.

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/22), 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/22). 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 22 is /pub/fedora/linux/updates/22.