Katello 4.1 Release Process

Development Releases
1

When Ready to Release

Release Owner

  • Request Hammer CLI Katello release from maintainers

  • Request Virt Who Configure release from maintainers

  • Change Redmine version 4.1.0 state to Closed

  • Do Cherry-picks: Clone tool_belt and run:

    • ./tools.rb setup-environment configs/katello/4.1.yaml
    • ./tools.rb cherry-picks --version 4.1.0 configs/katello/4.1.yaml
    • Open a PR in Katello release branch. Make sure the PR name starts with [CP] to prevent our automations from adding it to Redmine issues.
    • Using git cherry-pick -x as needed, verify tickets in the cherry_picks_4.1.0 file are accounted for, or additionally cherry-pick them.
    • For any cherry-picks that are not needed (including Redmine trackers) you can add them to the :ignores: section of tool_belt in configs/katello/4.1.yaml

  • Check for outdated deprecation warnings in the current and next release with ./tools check-deprecation-warnings configs/katello/4.1.yaml. Follow the instructions in the output of the command. Don’t forget to create any Redmine issues needed!

  • Bump version:

    • Open a PR (or use cherry-pick PR) against the release branch which updates lib/katello/version.rb to 4.1.0
    • Commit: git commit -m "Release 4.1.0"

  • In Katello release branch (the real one, not your fork), once PR is merged:

    • Tag: git tag -s -m "Release 4.1.0" 4.1.0
    • Push: git push upstream --follow-tags (Must be pushed directly to the release branch, as pull request merges will not preserve tags.)
    • Generate source gem: gem build katello.gemspec
    • Ensure you have a working login and password at rubygems.org
    • Push gem: gem push katello-4.1.0.gem

  • Email the delivery team informing them that the gem is published

Once Source is Available

Release Packager

Once release is out

Release Owner