Foreman 3.6.2 release process

Make this post a wiki (help)


Preparing code: 2023-08-08

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

Tagging a release: 2023-08-08

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: 2023-08-08

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: 2023-08-08

Release Owner

After the packages have been released

Release Owner

foreman-3.6-release-pipeline #6 [Jenkins] failed because it couldn’t provision a CentOS CI node. This is an ongoing issue we also see in nightly and currently blocks the release.

@Griffin-Sullivan you can proceed with preparing the release notes and we can merge the PRs once the release works.

1 Like

New attempt: foreman-3.6-release-pipeline #7 [Jenkins] is running now.

New attempt: foreman-3.6-release-pipeline #9 [Jenkins]