Foreman 3.5.1 release process

Make this post a wiki


Manual updates: 2022-12-16

Release Owner

Preparing code: 2022-12-16

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

Tagging a release: 2022-12-16

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: 2022-12-16

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

I think I found one missing item. On it still reads:

Unsupported releases

There is a release candidate available for testing.

    Foreman 3.5 & Katello 4.7

Looking at the source at foreman-documentation/index.adoc at master · theforeman/foreman-documentation · GitHub it seems there is some update missing, but I am not sure if this should be done manually so did not create a pull request.

Thanks! Here’s the PR to fix it short term:

And to include it properly in the process:

1 Like