From Fedora Project Wiki

 
Line 1: Line 1:
 +
 +
{{admon/important|This page is deprecated| All Fedora Release Engineering Documentation has moved [https://docs.pagure.org/releng/ here] with source hosted along side the code in the [https://pagure.io/releng releng pagure repository]}}
 
{{old}}
 
{{old}}
 
= Branching Freeze SOP =
 
= Branching Freeze SOP =

Latest revision as of 17:50, 3 November 2015

Important.png
This page is deprecated
All Fedora Release Engineering Documentation has moved here with source hosted along side the code in the releng pagure repository
Important.png
Old page
This page has been marked as "old", and likely contains content that is irrelevant or incorrect. If you can, please update this page. This page will be deleted if action is not taken.

Branching Freeze SOP

Introduction/Background

When the next release is branched from rawhide, it initially composes much like rawhide with nightly composes and no updates process.

Once the Alpha change freeze point is reached, bodhi is enabled for the branched release and updates are required.

  • Send announcement to devel-announce mailing list noting that the alpha change freeze is going to happen at least one day in advance.
  • Make sure all packages are signed.
  • Enable check for signed packages in mash config in puppet.
  • Koji tag changes here
  • Bodhi changes here

NOTE to updates pushers: In Change freeze only updates that fix accepted blockers or Freeze break bugs are allowed into the main tree. Please coordinate with QA for any stable updates pushes. Otherwise ONLY push updates-testing.