From Fedora Project Wiki
| Line 2: | Line 2: | ||
Release Engineering has freeze policies for each major release milestone: | Release Engineering has freeze policies for each major release milestone: | ||
* [[ReleaseEngineering/FeatureFreezePolicy| Feature Freeze Policy]] (One week before | * [[ReleaseEngineering/FeatureFreezePolicy| Feature Freeze Policy]] (One week before Alpha Freeze) | ||
* [[Alpha_Freeze_Policy| Alpha Freeze Policy]] | * [[Alpha_Freeze_Policy| Alpha Freeze Policy]] | ||
* [[ReleaseEngineering/StringFreezePolicy| String Freeze Policy]] (Same time as Alpha Freeze) | * [[ReleaseEngineering/StringFreezePolicy| String Freeze Policy]] (Same time as Alpha Freeze) | ||
Revision as of 19:05, 17 August 2009
Description
Release Engineering has freeze policies for each major release milestone:
- Feature Freeze Policy (One week before Alpha Freeze)
- Alpha Freeze Policy
- String Freeze Policy (Same time as Alpha Freeze)
- Final/Beta Freeze Policy
Packages which require an exception to freeze policies must be run through this SOP.
Action
The commands to tag a package properly once it has been accepted:
koji move-pkg --force dist-f40-updates-candidate dist-f40 <PKGNAME> koji tag-pkg --force f40-<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 does report success or failure. To verify, however, run these commands:
koji latest-pkg dist-f40 <PKGNAME> koji latest-pkg dist-f40-updates-candidate <PKGNAME>
Considerations
Refer to the development freeze policy for additional considerations. In particular, the freeze exception must be approved.