Foreman 1.19.0 process

Development Releases
1

Current release target: August 31st

Writing release notes

  • Update manual if applicable for any additional installation steps
  • Draft release notes in markdown (example), with these sections (and do not use personal pronouns):
    • 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
    • Release notes: bullet point list by category of most changes, excluding bug fixes for issues introduced during the release cycle, include link to bug numbers. You can auto-generate changes using the ‘changelog’ command in tool_belt
    • CLI release notes are taken from the hammer-cli and hammer-cli-foreman changelogs
    • Link to installer changelogs and note versions being used
  • Get the apipie doc and place it in api/1.19

Preparing code

  • Include Hammer CLI 0.14
  • Include a fix for #24628
  • 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. 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 1.19.0 state to Closed
  • List all issues targeted at the release, order by Closed date ascending and use git cherry-pick -x to cherry pick from develop to 1.19.0-stable branch
  • Clone tool_belt and run:
    • ./tools.rb setup-environment configs/foreman/1.19.yaml
    • ./tools.rb cherry-picks --version 1.19.0 configs/foreman/1.19.yaml
    • Verify tickets in the cherry_picks_1.19.0 file are accounted for or additional cherry pick them

Tagging a release

  • In foreman 1.19-stable:
    • Make sure test_1_19_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
    • change VERSION to 1.19.0
    • Run extras/changelog
    • Commit: git commit -m "Release 1.19.0"
    • Tag: git tag -s -m "Release 1.19.0" 1.19.0
    • Push: git push --follow-tags
  • In smart-proxy 1.19-stable:
    • Make sure test_proxy_1_19_stable is green
    • change VERSION to 1.19.0
    • Run extra/changelog
    • Commit: git commit -m "Release 1.19.0"
    • Tag: git tag -s -m "Release 1.19.0" 1.19.0
    • Push: git push --follow-tags
  • In foreman-selinux 1.19-stable:
    • change VERSION to 1.19.0
    • Run extras/changelog
    • Commit: git commit -m "Release 1.19.0"
    • Tag: git tag -s -m "Release 1.19.0" 1.19.0
    • Push: git push --follow-tags
  • In foreman-installer 1.19-stable:
    • change VERSION to 1.19.0
    • Commit: git commit -m "Release 1.19.0"
    • Tag: git tag -s -m "Release 1.19.0" 1.19.0
    • Push: git push --follow-tags
  • Run the Jenkins Tarballs Release to create tarballs
  • Verify tarballs are present on downloads.theforeman.org
  • Download, sign and upload detached signatures

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

  • In foreman-packaging rpm/1.19 branch, change foreman.spec, foreman-proxy.spec, foreman-selinux.spec, foreman-installer.spec:
    • Set version to “1.19.0”
    • Set release to “0.1%{?dotalpha…”, uncomment alphatag* (replace # with %), change to RC1
    • In each package dir, remove the old tarball, run spectool -g *.spec and git annex add *.tar.bz2
    • Commit with message “Release 1.19.0”
    • Submit a pull request
  • Update changelog files for debs:
    • scripts/changelog.rb -v 1.19.0-1 -m "1.19.0 released" debian/*/*/changelog
    • Submit a pull request
  • Trigger next step of release pipeline: release_packages
  • Use RPM_Packaging to sign RPMs
    • Download RPMs
    • Sign RPMs
    • Upload signatures
    • Upload RPMs
    • Sign “extra” RPMs
  • Trigger release_mash
  • Trigger release_test if mashing didn’t
  • Trigger release_push_deb and release_push_rpm if testing didn’t