Foreman 2.0.1 release process

Development Releases
1

Make this post a wiki

Manual updates

Preparing code

  • 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
  • Compare tagged packages in nightly vs. release koji tag and re-tag any updated dependencies that are required
  • 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 release field for any open Redmine tickets assigned to the release still (next minor, unset it or reject)
  • Change Redmine version 2.0.1 state to Closed
  • Ensure that code in git matches issues fixed in 2.0.1 in redmine. issues.rb can be used to generate a comparison between the two.

Tagging a release

  • In foreman 2.0-stable:
    • Make sure test_2_0_stable is green
    • 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 2.0.1
    • Push: git push upstream 2.0-stable --follow-tags
  • In smart-proxy 2.0-stable:
  • In foreman-selinux 2.0-stable:
    • Tag the release using tag.sh tag.sh 2.0.1
    • Push: git push upstream 2.0-stable --follow-tags
  • In foreman-installer 2.0-stable:
    • Tag the release using tag.sh tag.sh 2.0.1
    • Push: git push upstream 2.0-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