From Fedora Project Wiki

No edit summary
Line 1: Line 1:
== Description ==
== Description ==
Release Engineering has freeze policies for each major release milestone:
Packages which require an exception to freeze policies must be run through this SOP.
 
The following freeze policies are set for the following significant release milestones:


* [[ReleaseEngineering/FeatureFreezePolicy| Feature Freeze Policy]] (One week before Alpha Freeze)
* [[Feature_Freeze_Policy|Feature Freeze]]
* [[Alpha_Freeze_Policy| Alpha Freeze Policy]]  
* [[Alpha_Freeze_Policy |Alpha Freeze]]  
* [[ReleaseEngineering/StringFreezePolicy| String Freeze Policy]] (Same time as Alpha Freeze)
* [[String_Freeze_Policy |String Freeze]]
* [[ReleaseEngineering/FinalFreezePolicy| Final/Beta Freeze Policy]]
* [[Beta_Freeze_Policy  |Beta Freeze]]
* [[Final_Freeze_Policy  |Final Freeze]]


Packages which require an exception to freeze policies must be run through this SOP.
See [[Important_Release_Milestones|Important Release Milestones]] for a summary of all the freezes, dates, and exception handling.  


== Action ==
== Action ==
The commands to tag a package properly once it has been accepted:
The commands to tag a package properly once it has been accepted:
koji move-pkg --force dist-f{{FedoraVersion}}-updates-candidate dist-f{{FedoraVersion}} <PKGNAME>
<pre>
koji tag-pkg --force f{{FedoraVersion}}-<RELEASE> <PKGNAME>
$ koji move-pkg --force dist-f{{FedoraVersion}}-updates-candidate dist-f{{FedoraVersion}} <PKGNAME>
Where <PKGNAME> is the package name, and <RELEASE> is the first release in which the package should land (e.g. beta, preview, final).
$ koji tag-pkg --force f{{FedoraVersion}}-<RELEASE> <PKGNAME>
</pre>
Where <PKGNAME> is the package name, and <RELEASE> is the first release in which the package should land (e.g. beta, preview, final).


== Verification ==
== Verification ==
The {{command|koji}} client does report success or failure. To verify, however, run these commands:
The {{command|koji}} client reports success or failure. For secondary verification, run these commands:
koji latest-pkg dist-f{{FedoraVersion}} <PKGNAME>
<pre>
koji latest-pkg dist-f{{FedoraVersion}}-updates-candidate <PKGNAME>
$ koji latest-pkg dist-f{{FedoraVersion}} <PKGNAME>
 
$ koji latest-pkg dist-f{{FedoraVersion}}-updates-candidate <PKGNAME>
== Considerations ==
</pre>
Refer to the [[ReleaseEngineering/DevelFreezePolicy | development freeze policy]] for additional considerations.  In particular, the freeze exception must be approved.


== Consider Before Running ==
* Change agrees with stated policies (see links above)
* Approval for change has been granted


[[Category:Release Engineering SOPs]]
[[Category:Release Engineering SOPs]]

Revision as of 17:46, 8 January 2010

Description

Packages which require an exception to freeze policies must be run through this SOP.

The following freeze policies are set for the following significant release milestones:

See Important Release Milestones for a summary of all the freezes, dates, and exception handling.

Action

The commands to tag a package properly once it has been accepted:

$ koji move-pkg --force dist-f{{FedoraVersion}}-updates-candidate dist-f{{FedoraVersion}} <PKGNAME>
$ koji tag-pkg --force f{{FedoraVersion}}-<RELEASE> <PKGNAME>

Where <PKGNAME> is the package name, and <RELEASE> is the first release in which the package should land (e.g. beta, preview, final).

Verification

The koji client reports success or failure. For secondary verification, run these commands:

$ koji latest-pkg dist-f{{FedoraVersion}} <PKGNAME>
$ koji latest-pkg dist-f{{FedoraVersion}}-updates-candidate <PKGNAME>

Consider Before Running

  • Change agrees with stated policies (see links above)
  • Approval for change has been granted