release_notes.md

Update release document (find url from ehelms)

Release in redmine (KATELLO_3.5.0)

closed issues are definitely in

Announce branching

2 weeks prior

Branching (master -> KATELLO-3.5)

repos:

• katello
• katello-packaging
• katello-installer
  • kind of special
  • puppet modules need to be built
• hammer-cli-katello --> cut a release via ehelms/tool_belt

Koji tag creation

via tool_belt

Example: create a tool_belt config for 3.5 noop and a commit stage

---

How tool_belt creates tags

katello-nightly-rhel7-build katello-nightly-rhel7 katello-nightly-override katello-nightly-thirdparty foreman-nightly-rhel7 foreman-nightly-plugins-rhel7

external repos (for dependencies)

• rhel7
• epel

lib/katello/version.rb must match tag

build target == repo in koji tag <--> package -> has many builds

build config first, open PR in tool_belt (use 3.4 as a reference)

There may be some downtime after branching/tagging (work will be from triage)

Copy docs from nightly to 3.5

in theforeman.org generate API docs from KATELLO_3.5 branch get the PR merged

Make release notes

Look at redmine issues

• Find features
• Find large bugs

Use release_notes doc in plugins/katello in theforeman.org repo create sections for everything ping people to fill in release notes for features

Towards making the RC

2 weeks after branching, you want to be releasing the RC

• pulling in cherry picks
  • Find all the cherry-pick (via tool_belt)
  • cherry-pick them
  • open PRs in each project to test
• Merge, bump version, tag, build, release, source
• Update packaging repo with PR for new sources (tests will run)
  • update katello, rubygem-katello, katello-installer, (katello-release) repos

Mash (making the repos)

• in katello-packaging comp/*.xml - shouldn't have to edit them list all packages that should end up in the repo
• koji packages -> comps -> repos
• lives at koji.katello.org/releases

Test the packages (in forklift)

• pipeline playbooks
  • self-contained, spin up vagrant vms, install server/capsule, run bats
  • Create 3:
    • 3.5
    • upgrade.34_35
    • upgrade.33_35