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)) |
(milestone freezes) |
||
| (6 intermediate revisions by the same user not shown) | |||
| 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: | ||
* [[ | * [[Milestone freezes |Alpha Freeze]] | ||
* [[String_Freeze_Policy |String Freeze]] | * [[String_Freeze_Policy |String Freeze]] | ||
* [[ | * [[Milestone freezes |Beta Freeze]] | ||
* [[ | * [[Milestone freezes |Final Freeze]] | ||
See [[ | See [[Fedora Release Life Cycle]] for a summary of all the freezes, dates, and exception handling, or the release engineering [https://fedorapeople.org/groups/schedule/f-{{FedoraVersionNumber|next}}/f-{{FedoraVersionNumber|next}}-releng-tasks.html calendar for the current release]. | ||
== 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: | ||
{{#tag:pre| | |||
$ koji move-pkg --force dist-f{{ | $ koji move-pkg --force dist-f{{FedoraVersionNumber|next}}-updates-candidate dist-f{{FedoraVersionNumber|next}} <PKGNAME> | ||
$ koji tag-pkg --force f{{ | $ koji tag-pkg --force f{{FedoraVersionNumber|next}}-<RELEASE> <PKGNAME> | ||
}} | |||
Where <PKGNAME> is the package name, and <RELEASE> is the first release in which the package should land (e.g. beta | Where <PKGNAME> is the package name, and <RELEASE> is the first release in which the package should land (e.g. alpha, beta, final). | ||
== Verification == | == Verification == | ||
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| | |||
$ 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> | ||
}} | |||
== Consider Before Running == | == Consider Before Running == | ||
* Change agrees with stated policies (see links above) | * Change agrees with stated policies (see links above) | ||
* Approval for change has been granted | * Approval for change has been granted under [[QA:SOP_blocker_bug_process]] or [[QA:SOP_freeze_exception_bug_process]] | ||
[[Category:Release Engineering SOPs]] | [[Category:Release Engineering SOPs]] | ||
Revision as of 22:47, 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