Foreman 3.9.3 release process

Make this post a wiki (help)


Preparing code: 2024-04-26

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

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

Tagging a release: 2024-04-26

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-04-26

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

Manual updates: 2024-04-26

Release Owner

After the packages have been released

Release Owner

Docs updates are up. Waiting for release engineering to publish packages.

@ekohl Release engineering work seems to be done. We can continue with the PRs above.