Breaking development freeze SOP: Difference between revisions

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

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

@@ Line 1: / Line 1: @@
-<!-- page was renamed from ReleaseEngineering/RelEngSOPTemplate
+{{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 ==
-<!-- page was renamed from ReleaseEngineering/SOP/RelEngSOPTemplate
+Packages which require an exception to freeze policies must be run through this SOP.
--->
-= Topic - SOP =
+The following freeze policies are set for the following significant release milestones:
-== Description ==
+* [[Milestone freezes    |Alpha Freeze]]
-<!-- Put a description of the task here.
+* [[String_Freeze_Policy |String Freeze]]
--->
+* [[Milestone freezes    |Beta Freeze]]
+* [[Milestone freezes    |Final Freeze]]
+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 ==
-<!-- Describe the action and provide examples
+The commands to tag a package properly once it has been accepted:
--->
+{{#tag:pre|
+$ koji move-pkg --force dist-f{{FedoraVersionNumber|next}}-updates-candidate dist-f{{FedoraVersionNumber|next}} <PKGNAME>
+$ 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. alpha, beta, final).
 == Verification ==
-<!-- Provide a method to verify the action was successful
+The {{command|koji}} client reports success or failure. For secondary verification, run these commands:
--->
+{{#tag:pre|
+$ koji latest-pkg dist-f{{FedoraVersionNumber|next}} <PKGNAME>
+$ koji latest-pkg dist-f{{FedoraVersionNumber|next}}-updates-candidate <PKGNAME>
+}}
-== Considerations ==
+== Consider Before Running ==
-<!-- Create a list of things to keep in mind when performing action.
+* 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]]
-<!-- Be sure to remove the Category listed below.
--->
-----
-[[Category:Template]]
 [[Category:Release Engineering SOPs]]

Search