Breaking development freeze SOP: Difference between revisions

Revision as of 05:10, 25 September 2014

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.

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).

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>

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

@@ Line 9: / Line 9: @@
 * [[Change_deadlines     |Final change deadline]]
-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 ==