|
|
| Line 1: |
Line 1: |
| == Description == | | == Description == |
| Release Engineering has a [[ReleaseEngineering/DevelFreezePolicy | development freeze policy]]. Packages which require an exception to the development freeeze must be run through this SOP.
| | <!-- Put a description of the task here. --> |
|
| |
|
| == Action == | | == Action == |
| The commands to tag a package properly once it has been accepted:
| | <!-- Describe the action and provide examples --> |
| koji move-pkg --force dist-f{{FedoraVersion}}-updates-candidate dist-f{{FedoraVersion}} <PKGNAME>
| |
| koji tag-pkg --force f{{FedoraVersion}}-<RELEASE> <PKGNAME>
| |
| Where <PKGNAME> is the package name, and <RELEASE> is the first release in which the package should land (e.g. beta, preview, final).
| |
|
| |
|
| == Verification == | | == Verification == |
| The {{command|koji}} client does report success or failure. To verify, however, run these commands:
| | <!-- Provide a method to verify the action was successful --> |
| koji latest-pkg dist-f{{FedoraVersion}} <PKGNAME>
| |
| koji latest-pkg dist-f{{FedoraVersion}}-updates-candidate <PKGNAME>
| |
|
| |
|
| == Considerations == | | == Considerations == |
| Refer to the [[ReleaseEngineering/DevelFreezePolicy | development freeze policy]] for additional considerations. In particular, the freeze exception must be approved.
| | <!-- Create a list of things to keep in mind when performing action. --> |
|
| |
|
| | <!-- Be sure to remove the Category:Template link below. Keep the RelEng SOP category link. --> |
|
| |
|
| | [[Category:Template]] |
| [[Category:Release Engineering SOPs]] | | [[Category:Release Engineering SOPs]] |
