Katello 4.0.3 Release Process

Development Releases
1

Roles

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

Once release is out

Release Owner

2 Likes