From Fedora Project Wiki

(fix templates in code, thanks to a kparal comment on an old jlaska blog post...amazing what you find in google searches)
(milestone freezes)
(3 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:


* [[Change_deadlines    |Alpha change deadline]]  
* [[Milestone freezes    |Alpha Freeze]]  
* [[String_Freeze_Policy |String Freeze]]
* [[String_Freeze_Policy |String Freeze]]
* [[Change_deadlines    |Beta change deadline]]
* [[Milestone freezes    |Beta Freeze]]
* [[Change_deadlines    |Final change deadline]]
* [[Milestone freezes    |Final Freeze]]


See [[Important_Release_Milestones|Important Release Milestones]] for a summary of all the freezes, dates, and exception handling.  
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 ==
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{{FedoraVersion}} <PKGNAME>
$ koji latest-pkg dist-f{{FedoraVersionNumber|next}} <PKGNAME>
$ koji latest-pkg dist-f{{FedoraVersion}}-updates-candidate <PKGNAME>
$ koji latest-pkg dist-f{{FedoraVersionNumber|next}}-updates-candidate <PKGNAME>
}}
}}



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