Foreman 3.1.0(GA) release process

[upadhyeammit]

Make this post a wiki

Roles

• Release Owner: @upadhyeammit
• Release Engineer: @Odilhao
• Installer Maintainer: @

Manual updates: 2021-12-08

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.

Preparing code: 2021-12-08

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

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

Tagging a release: 2021-12-08

Release Owner

• In foreman 3.1-stable:
  • Make sure test_3_1_stable is green
  • run make -C locale tx-update There are no new translations to pull
  • Tag the release using tag.sh tag.sh 3.1.0 && 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.0 && git push upstream 3.1-stable --follow-tags
• In foreman-selinux 3.1-stable:
  • Tag the release using tag.sh tag.sh 3.1.0 && git push upstream 3.1-stable --follow-tags
• In foreman-installer 3.1-stable:
  • Tag the release using tag.sh tag.sh 3.1.0 && git push upstream 3.1-stable --follow-tags
• Run the Jenkins Tarballs Release to create tarballs

Release Engineer

• 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: 2021-12-08

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

Background documentation

• Update foreman-packaging branches
  • rpm/3.1
  • deb/3.1
• Wait for packages to be built
  • rpm/3.1
  • deb/3.1
• Tag foreman-release into foreman-client-3.1-rhel7 and foreman-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.0-1.el7
  • koji tag-build foreman-client-3.1-el8 foreman-release-3.1.0-1.el8
• Check for outstanding PRs against 3.1 packaging, and merge if possible:
  • rpm/3.1
  • deb/3.1
• 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

Release Owner

• Update the versions on the website in version and latest news
• Update the foreman_version to 3.1 in website’s _config.yml file
• 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
• 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.