Foreman 1.24.3 release process

Development Releases
1

Make this post a wiki

Manual updates

Preparing code

  • Remove/change release field for any open Redmine tickets assigned to the release still (next minor, unset it or reject)
  • Change Redmine version 1.24.3 state to Closed
  • Ensure that code in git matches issues fixed in 1.24.3 in redmine. issues.rb can be used to generate a comparison between the two.

Tagging a release

  • In foreman 1.24-stable:
    • Make sure test_1_24_stable is green
    • run make -C locale tx-update (if Transifex has not switched to the next major release yet, usually after .2)
    • run script/sync_templates.sh
    • update template snapshots with rake snapshots:generate RAILS_ENV=test and verify changes are expected
    • Tag the release using tag.sh tag.sh 1.24.3
    • Push: git push upstream 1.24-stable --follow-tags
  • In smart-proxy 1.24-stable:
  • In foreman-selinux 1.24-stable:
    • Tag the release using tag.sh tag.sh 1.24.3
    • Push: git push upstream 1.24-stable --follow-tags
  • In foreman-installer 1.24-stable:
    • Tag the release using tag.sh tag.sh 1.24.3
    • Push: git push upstream 1.24-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

Background documentation