When Ready to Release
Release Owner
-
Request Hammer CLI Katello release from maintainers
-
Request Virt Who Configure release from maintainers
-
Clone tool_belt and run:
-
./tools.rb setup-environment configs/katello/4.1.yaml -
./tools.rb cherry-picks --version 4.1.0-rc2 configs/katello/4.1.yaml - Verify tickets in the cherry_picks_4.1.0-rc2 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.1.yaml. Follow the instructions in the output of the command.
-
-
In katello release branch:
-
Update
lib/katello/version.rbto 4.1.0-rc2 -
Commit:
git commit -m "Release 4.1.0-rc2" -
Tag:
git tag -s -m "Release 4.1.0-rc2" 4.1.0-rc2 -
Push:
git push --follow-tags -
Generate source gem:
gem build katello.gemspec -
Push gem:
gem push katello-4.1.0-rc2.gem
-
Update
Once Source is Available
Release Packager
-
Update
katello,katello-reposandrubygem-katelloin foreman-packaging rpm/4.1 branch. - Merge packaging PR once job is green
-
Release all packages:
obal release katello katello-repos rubygem-katello - 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
