Foreman 2.2.0 release process

[upadhyeammit]

Make this post a wiki

Manual updates

• 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.
• Update installer options section using the get-params script (Note: this step can only be done after packages are released)

Preparing code

• 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
• 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 2.2.0 in redmine. issues.rb can be used to generate a comparison between the two.
• Change Redmine version 2.2.0 state to Closed

Tagging a release

• In foreman 2.2-stable:
  • Make sure test_2_2_stable is green
  • run make -C locale tx-update
  • Tag the release using tag.sh tag.sh 2.2.0 && git push upstream 2.2-stable --follow-tags
• In smart-proxy 2.2-stable:
  • Make sure test_proxy_2_2_stable is green
  • Tag the release using tag.sh tag.sh 2.2.0 && git push upstream 2.2-stable --follow-tags
• In foreman-selinux 2.2-stable:
  • Tag the release using tag.sh tag.sh 2.2.0 && git push upstream 2.2-stable --follow-tags
• In foreman-installer 2.2-stable:
  • Tag the release using tag.sh tag.sh 2.2.0 && git push upstream 2.2-stable --follow-tags
• Run the Jenkins Tarballs Release to create tarballs
• Update release version similar to here
• Sign Tarballs
  • Download
  • Inspect
  • Sign and upload detached signatures

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

Background documentation

• Update foreman-packaging
  • rpm/2.2
  • deb/2.2 branches
• Trigger release_packages in Jenkins by calling release_packages script.
• Tag foreman-release into foreman-client-2.2-rhel7 and foreman-client-2.2-el8, as this doesn’t happen automatically for those tags.
  • koji tag-build foreman-client-2.2-rhel7 foreman-release-2.2.0-1.el7
  • koji tag-build foreman-client-2.2-el8 foreman-release-2.2.0-1.el8
• Sign the RPMs in the release
  • Download
  • Sign
  • Upload RPM signatures
  • Upload RPMs
• Sign RPMs for client repos (call scripts with PROJECT=client)
  • Download
  • Sign
  • Upload RPM signatures
  • Upload RPMs
• 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

• 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
• After about a week, update stable version in foreman-infra