| |
@@ -0,0 +1,62 @@
|
| |
+
|
| |
+
|
| |
+ Find ostree version and pungi compose ID for the media we want to release.
|
| |
+
|
| |
+ Look under https://kojipkgs.fedoraproject.org/compose/twoweek/
|
| |
+ Right now there are a few different ways to figure out what the ostree version is/should be:
|
| |
+
|
| |
+ - boot media from a compose and run rpm-ostree status
|
| |
+ - look at autocloud raw results (the commit/version is in there)
|
| |
+ - look at http://ostree-signed-commit-checker-ostree-commit-checker.origin.dustymabe.com/
|
| |
+ to see what the latest version is in the repos and assume that version is what is in
|
| |
+ the media
|
| |
+
|
| |
+
|
| |
+ Example ostree version: 27.25
|
| |
+ Example pungi compose ID: Fedora-Atomic-27-20171211.0
|
| |
+
|
| |
+
|
| |
+ Before sending out candidate email:
|
| |
+
|
| |
+ - Check to make sure the compose state is FINISHED and not FINISHED_INCOMPLETE or any other state
|
| |
+ - ex: https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-27-20171211.0/STATUS
|
| |
+ - Check to make sure media from all architectures have the same ostree version
|
| |
+ - Can do this by booting the media (or ask ksinny)
|
| |
+ - Check to see if latest ostree pass a-h-t
|
| |
+ - https://github.com/projectatomic/atomic-host-tests
|
| |
+ - Check to see if latest cloud images pass autocloud
|
| |
+ - https://apps.fedoraproject.org/autocloud/compose
|
| |
+ - Check to see if ISO image tests passed in OpenQA
|
| |
+ - http://openqa.fedoraproject.org/
|
| |
+ - Check to make sure AMIs were published for every region for that compose
|
| |
+ - use: https://pagure.io/fedora-websites/blob/master/f/tools/get_ami.py
|
| |
+ - Run an openshift test againt the latest AMI
|
| |
+ - something like: http://www.projectatomic.io/blog/2016/12/part1-install-origin-on-f25-atomic-host/
|
| |
+ - Usually check with jbrooks to see if kube works
|
| |
+ - talk with jbrooks
|
| |
+
|
| |
+ If all of those tests pass then:
|
| |
+
|
| |
+ - Send out candidate email. Example:
|
| |
+ - example: https://lists.projectatomic.io/projectatomic-archives/atomic-devel/2017-November/msg00087.html
|
| |
+
|
| |
+ Request Release:
|
| |
+
|
| |
+ - make request to releng to do the release:
|
| |
+ - example: https://pagure.io/releng/issue/7189
|
| |
+ - talk with mohan in #fedora-releng irc channel to sync up
|
| |
+ - mostly, "hey I created this ticket, can we make sure we run the release
|
| |
+ before we start bodhi pushes for the day".
|
| |
+
|
| |
+ After release:
|
| |
+
|
| |
+ - Update Vagrant Boxes in Vagrant Cloud (only Dusty has credentials for now)
|
| |
+ - issue for having us automate this via API calls: https://pagure.io/atomic-wg/issue/393
|
| |
+ - Send out "follow up" email:
|
| |
+ - example: https://lists.projectatomic.io/projectatomic-archives/atomic-devel/2017-November/msg00092.html
|
| |
+ - Verify static delta works for upgrade from previous release
|
| |
+
|
| |
+
|
| |
+ Dusty
|
| |
+
|
| |
+
|
| |
