From Fedora Project Wiki
(update the 'freeze' links to 'change deadlines' (which i'm going to change again soon if all goes well, but oh well)) |
(the 'feature freeze' doesn't exist in the form of something that requires freeze exceptions any more.) |
||
| Line 4: | Line 4: | ||
The following freeze policies are set for the following significant release milestones: | The following freeze policies are set for the following significant release milestones: | ||
* [[Change_deadlines |Alpha change deadline]] | * [[Change_deadlines |Alpha change deadline]] | ||
* [[String_Freeze_Policy |String Freeze]] | * [[String_Freeze_Policy |String Freeze]] | ||
Revision as of 04:58, 25 September 2014
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