Make this post a wiki
Roles
- Release Owner: @upadhyeammit
- Release Engineer: @Odilhao
- Installer Maintainer: @ekohl
Manual updates: 2022-02-22
Release Engineer
- Update manual if applicable for any additional installation steps
- Update release notes section in the manual:
- Release notes: bullet point list by category of all changes, include link to bug numbers. You can auto-generate changes using the release notes script.
- CLI release notes are taken from the hammer-cli and hammer-cli-foreman changelogs
- Link to installer changelogs and note versions being used
- Update installer options section using the get-params script if any changes were made in the installer or installer modules (after new packages have been released)
- Update the apipie docs and place those in the foreman/3.1/apidoc directory if any changes were made to the API
Preparing code: 2022-02-22
Installer Maintainer
-
Make patch releases of installer modules that have important changes
- Branch to MAJ.MIN-stable if recent changes to the module aren’t suitable for patch (x.y.z) release
Release Owner
- Add a new Redmine version for the next minor, unless the series is EOL. Be sure the version is set to sharing with subprojects.
- Remove/change target version field for any open Redmine tickets assigned to the release still (next minor, unset it or reject)
- Ensure that code in git matches issues fixed in 3.1.2 in redmine. issues.rb can be used to generate a comparison between the two.
- Change Redmine version 3.1.2 state to Closed
Tagging a release: 2022-02-22
Release Owner
- In foreman 3.1-stable:
- Make sure test_3_1_stable is green
-
Tag the release using tag.sh
tag.sh 3.1.2 && git push upstream 3.1-stable --follow-tags
- In smart-proxy 3.1-stable:
- Make sure test_proxy_3_1_stable is green
-
Tag the release using tag.sh
tag.sh 3.1.2 && git push upstream 3.1-stable --follow-tags
- In foreman-selinux 3.1-stable:
-
Tag the release using tag.sh
tag.sh 3.1.2 && git push upstream 3.1-stable --follow-tags
-
Tag the release using tag.sh
- In foreman-installer 3.1-stable:
-
Tag the release using tag.sh
tag.sh 3.1.2 && git push upstream 3.1-stable --follow-tags
-
Tag the release using tag.sh
- Run the Jenkins Tarballs Release to create tarballs
Release Engineer
- Update release version similar to here
- Sign Tarballs
Note: If for some reason there was an issue with the tarballs that required uploading new tarballs, CDN cache should be invalidated so that the builders use the updated tarballs.
Packaging a release: 2022-02-22
Note it is considered good practice to release on a day when the next day is a working day. This means no releases on Fridays or on the day before a holiday.
Release Engineer
- Update foreman-packaging branches
- Wait for packages to be built
-
Tag
foreman-releaseintoforeman-client-3.1-rhel7andforeman-client-3.1-el8, as this doesn’t happen automatically for those tags.-
koji tag-build foreman-client-3.1-rhel7 foreman-release-3.1.2-1.el7 -
koji tag-build foreman-client-3.1-el8 foreman-release-3.1.2-1.el8
-
- Check for outstanding PRs against 3.1 packaging, and merge if possible:
- Sign the RPMs in the release
-
Sign RPMs for client repos (call scripts with
PROJECT=client) -
Kick off the release pipeline by calling
release_pipeline -
Kick off the client pipeline by calling
PROJECT=client release_pipeline - Kick off the plugins pipeline by calling plugins_pipeline
After the packages have been released
Release Owner
- Update the versions on the website in version and latest news
- Announce the release on Discourse
- Update the topic in #theforeman channel on Freenode
- Share the release announcement on twitter
- Release pipeline will trigger foreman-plugins-3.1-deb-test-pipeline and foreman-plugins-3.1-rpm-test-pipeline. These don’t block releases but can be used to understand known issues around plugin compatibility with Foreman 3.1.