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-f40-updates-candidate dist-f40 <PKGNAME>
$ koji tag-pkg --force f40-<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-f40 <PKGNAME>
$ koji latest-pkg dist-f40-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: @@
+{{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 ==
-Release Engineering has freeze policies for each major release milestone:
+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:
-* [[ReleaseEngineering/FeatureFreezePolicy|  Feature Freeze Policy]] (One week before Feature Freeze)
+* [[Milestone freezes    |Alpha Freeze]]
-* [[Alpha_Freeze_Policy|  Alpha Freeze Policy]]
+* [[String_Freeze_Policy |String Freeze]]
-* [[ReleaseEngineering/StringFreezePolicy|  String Freeze Policy]] (Same time as Alpha Freeze)
+* [[Milestone freezes    |Beta Freeze]]
-* [[ReleaseEngineering/FinalFreezePolicy|  Final/Beta Freeze Policy]]
+* [[Milestone freezes    |Final Freeze]]
-Packages which require an exception to freeze policies must be run through this SOP.
+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 ==
 The commands to tag a package properly once it has been accepted:
- koji move-pkg --force dist-f{{FedoraVersion}}-updates-candidate dist-f{{FedoraVersion}} <PKGNAME>
+{{#tag:pre|
- koji tag-pkg --force f{{FedoraVersion}}-<RELEASE> <PKGNAME>
+$ koji move-pkg --force dist-f{{FedoraVersionNumber|next}}-updates-candidate dist-f{{FedoraVersionNumber|next}} <PKGNAME>
-Where <PKGNAME> is the package name, and <RELEASE> is the first release in which the package should land (e.g. beta, preview, final).
+$ 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 ==
-The {{command|koji}} client does report success or failure. To verify, however, run these commands:
+The {{command|koji}} client reports success or failure. For secondary verification, run these commands:
- koji latest-pkg dist-f{{FedoraVersion}} <PKGNAME>
+{{#tag:pre|
- koji latest-pkg dist-f{{FedoraVersion}}-updates-candidate <PKGNAME>
+$ koji latest-pkg dist-f{{FedoraVersionNumber|next}} <PKGNAME>
+$ koji latest-pkg dist-f{{FedoraVersionNumber|next}}-updates-candidate <PKGNAME>
-== Considerations ==
+}}
-Refer to the [[ReleaseEngineering/DevelFreezePolicy | development freeze policy]] for additional considerations.  In particular, the freeze exception must be approved.
+== 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]]
 [[Category:Release Engineering SOPs]]

Search