Katello 4.2.0 GA release process

Development Releases
1

Roles

  • Release Owner: @jlsherrill
  • Release Engineer: @pcreech

When Ready to Release

Release Owner

  • Request Hammer CLI Katello release from maintainers

  • Request Virt Who Configure release from maintainers

  • Request any other releases as needed from the release owners (consult the :repos: section of configs/katello/4.2.yaml)

  • Change Redmine version 4.2.0 state to Closed

  • Do Cherry-picks: Clone tool_belt

    • If any minor versions of Katello have been added to Redmine since the last cherry-pick, make sure to include them in prior_releases in configs/katello/4.2.yaml
    • Run ./tools.rb setup-environment configs/katello/4.2.yaml
    • Run ./tools.rb cherry-picks --version 4.2.0 configs/katello/4.2.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.2.0 file are accounted for, or additionally cherry-pick them. Recommended: Do this in tool_belt’s checkout of Katello, in repos/katello/4.2.0/katello. This way when you run cherry-picks again, tool_belt will be aware of any picks already completed.
    • 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.2.yaml

  • Check for outdated deprecation warnings in the current and next release with ./tools check-deprecation-warnings configs/katello/4.2.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.2.0
    • git pull to make sure you have the latest changes
    • Commit: git commit -m "Release 4.2.0"
    • Ensure that the commit above is the last commit and there are no commits after it. This is the commit that will get tagged. (Rearrange commits with git rebase -i if needed.)

  • Once the PR is merged, perform the following in the Katello release branch (the real one, not your fork):

    • Tag: git tag -s -m "Release 4.2.0" 4.2.0
    • Push: git push --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.2.0.gem

  • Inform the delivery team that the gem is published

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

1 Like
2

Did the 4.2.0 release stall? Or has it been completed without fanfare? I don’t see any news about it for a week or so.

3

Hello!

I was giving a week for rc3, and then had a bit of PTO. Evertyhing is built, but the pipelines are having some issues:

https://ci.theforeman.org/job/katello-4.2-rpm-pipeline/

that we are trying to work through.

2 Likes
4

Hi,

Did 4.2.0 GA make it out? I see what look like GA release packages in the yum repo, but no announcement of the release at this point.

Apologies if I’m interrupting in the middle of things. Just want to know if I can install 4.2.0 GA or if these packages have made their way into the repo by mistake.

Cheers

5

It was released, but was on PTO at the time :slight_smile: Announcement has now been made!