Foreman 3.2.0(GA) release process

Make this post a wiki


Manual updates: 2022-03-15

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.
    • Headline features: half a dozen important features with a few sentences description each
      Generate the apipie docs and raise pull request in apidocs repository

Preparing code: 2022-03-15

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

Tagging a release: 2022-03-15

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 && 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 && git push upstream 3.2-stable --follow-tags
  • In foreman-installer 3.2-stable:
    • Tag the release using 3.2.0 && 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-03-15

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

After the packages have been released

Release Owner

RPMs and debian packages have been pushed :slight_smile: