From Fedora Project Wiki
(better links for dates) |
(doh) |
||
| Line 22: | Line 22: | ||
The {{command|koji}} client reports success or failure. For secondary verification, run these commands: | The {{command|koji}} client reports success or failure. For secondary verification, run these commands: | ||
{{#tag:pre| | {{#tag:pre| | ||
$ koji latest-pkg dist-f{{ | $ koji latest-pkg dist-f{{FedoraVersionNumber|next}} <PKGNAME> | ||
$ koji latest-pkg dist-f{{ | $ koji latest-pkg dist-f{{FedoraVersionNumber|next}}-updates-candidate <PKGNAME> | ||
}} | }} | ||
Revision as of 05:11, 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 Fedora Release Life Cycle for a summary of all the freezes, dates, and exception handling, or the release engineering calendar for the current release.
Action
The commands to tag a package properly once it has been accepted:
$ koji move-pkg --force dist-f41-updates-candidate dist-f41 <PKGNAME> $ koji tag-pkg --force f41-<RELEASE> <PKGNAME>
Where <PKGNAME> is the package name, and <RELEASE> is the first release in which the package should land (e.g. alpha, beta, final).
Verification
The koji client reports success or failure. For secondary verification, run these commands:
$ koji latest-pkg dist-f41 <PKGNAME> $ koji latest-pkg dist-f41-updates-candidate <PKGNAME>
Consider Before Running
- Change agrees with stated policies (see links above)
- Approval for change has been granted under QA:SOP_blocker_bug_process or QA:SOP_freeze_exception_bug_process