Katello 4.0.3 Release Process

[jjeffers]

Roles

• Release Owner: @jjeffers
• Release Engineer: @pcreech

When Ready to Release

Release Owner

• Request Hammer CLI Katello release from maintainers

• Request Virt Who Configure release from maintainers

• Change Redmine version 4.0.3 state to Closed

• Clone tool_belt and run:

  • ./tools.rb setup-environment configs/katello/4.0.yaml
  • ./tools.rb cherry-picks --version 4.0.3 configs/katello/4.0.yaml
  • Verify tickets in the cherry_picks_4.0.3 file are accounted for or additional cherry pick them
  • Check for outdated deprecation warnings in the current and next release with ./tools check-deprecation-warnings configs/katello/4.0.yaml. Follow the instructions in the output of the command.

• In katello release branch:

  • Update lib/katello/version.rb to 4.0.3
  • Commit: git commit -m "Release 4.0.3"
  • Tag: git tag -s -m "Release 4.0.3" 4.0.3
  • Push: git push --follow-tags
  • Generate source gem: gem build katello.gemspec
  • Push gem: gem push katello-4.0.3.gem

Once Source is Available

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

• Update release version similar to here
• Update katello, katello-repos and rubygem-katello
  • PROJECT=katello VERSION=4.0 ./bump_rpm_packaging
• Merge packaging PR once job is green
• Wait for Jenkins to build the packages (replace 4.0 with the matching Foreman version)
• Download, sign, upload RPM signatures and upload RPMs
• Kick off the release pipeline by calling release_pipeline

Once release is out

Release Owner

• Create and upload release specific developer stable box