Foreman 3.11.0-rc2 release process

Make this post a wiki (help)


Preparing code: 2024-06-04

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

Tagging a release: 2024-06-04

Release Owner

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: 2024-06-04

Release Engineer

Background documentation

Manual updates: 2024-06-04

Release Owner

After the packages have been released

Release Owner

Skipping this and translations since my foreman setup is super messed up right now.