From Fedora Project Wiki
(milestone freezes) |
Maxamillion (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
{{admon/important|This page is deprecated| All Fedora Release Engineering Documentation has moved [https://docs.pagure.org/releng/ here] with source hosted along side the code in the [https://pagure.io/releng releng pagure repository]}} | |||
== Description == | == Description == | ||
Packages which require an exception to freeze policies must be run through this SOP. | Packages which require an exception to freeze policies must be run through this SOP. | ||
Latest revision as of 17:51, 3 November 2015
This page is deprecated
All Fedora Release Engineering Documentation has moved here with source hosted along side the code in the releng pagure repository
All Fedora Release Engineering Documentation has moved here with source hosted along side the code in the releng pagure repository
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-f42-updates-candidate dist-f42 <PKGNAME> $ koji tag-pkg --force f42-<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-f42 <PKGNAME> $ koji latest-pkg dist-f42-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