Foreman 2.5.0 release process

Make this post a wiki

Manual updates: 2021-06-02

  • 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.
    • CLI release notes are taken from the hammer-cli and hammer-cli-foreman changelogs
    • Link to installer changelogs and note versions being used
    • Headline features: half a dozen important features with a few sentences description each
    • Upgrade notes: all important notices that users must be aware of before upgrading
  • Update installer options section using the get-params script (Note: this step can only be done after packages are released)
  • Generate the apipie doc and place it in the api/2.5 directory

Preparing code: 2021-06-02

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

Tagging a release: 2021-06-02

  • In foreman 2.5-stable:
    • Make sure test_2_5_stable is green
    • run make -C locale tx-update
    • Tag the release using 2.5.0 && git push upstream 2.5-stable --follow-tags
  • In smart-proxy 2.5-stable:
  • In foreman-selinux 2.5-stable:
    • Tag the release using 2.5.0 && git push upstream 2.5-stable --follow-tags
  • In foreman-installer 2.5-stable:
    • Tag the release using 2.5.0 && git push upstream 2.5-stable --follow-tags
  • Run the Jenkins Tarballs Release to create tarballs
  • Update release version similar to here
  • Sign Tarballs

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: 2021-06-02

Background documentation

After the packages have been released

I kicked off foreman-2.5-release-pipeline [Jenkins], but there was a maintenance, and I think I’ve seen jobs failing after that :confused:

I kicked off foreman-2.5-release-pipeline #9 [Jenkins]

And I opened Issue #348: foreman-ci-slave01 fails to run GitSCM plugin - centos-infra - after talking to Arrfab on #centos-ci

1 Like

Arrfab fixed Jenkins, and I’ve kicked off foreman-2.5-release-pipeline #10 [Jenkins]