Foreman 3.2.0-rc1 release process

Make this post a wiki


Manual updates: 2022-02-14

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
    • Headline features: half a dozen important features with a few sentences description each
    • Upgrade notes: all important notices that users must be aware of before upgrading
  • Update installer options section using the get-params script (Note: this step can only be done after packages are released)
    Generate the apipie docs and raise pull request in apidocs repository

Preparing code: 2022-02-14

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.2.0-rc1 in redmine. issues.rb can be used to generate a comparison between the two.

Tagging a release: 2022-02-14

Release Owner

  • In foreman 3.2-stable:
    • Make sure test_3_2_stable is green
    • run make -C locale tx-update
    • Tag the release using 3.2.0-rc1 && git push upstream 3.2-stable --follow-tags
  • In smart-proxy 3.2-stable:
  • In foreman-selinux 3.2-stable:
    • Tag the release using 3.2.0-rc1 && git push upstream 3.2-stable --follow-tags
  • In foreman-installer 3.2-stable:
    • Tag the release using 3.2.0-rc1 && git push upstream 3.2-stable --follow-tags
  • Run the Jenkins Tarballs Release to create tarballs

Release Engineer

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-14

Release Engineer

Background documentation

After the packages have been released

Release Owner

I’ve managed to make it most of the way through the release process, the last remaining issue being have our release pipeline have a complete run. For now though it seems that Centos infra is having issues which leaves us unable to properly run parts of the release process. Hopefully these issues will clear up by tomorrow and we can finish the process.

I’m having another issue with the deb release though, where it seems to be unable to find a version of Kafo to properly use which I’ll try and ask better deb minds what may be occuring there. :slight_smile: