Katello 3.11 Branch Process

Development Releases
1

Release Owner

Release Packager

  • Ensure tool_belt config is merged and output from ./tools.rb koji configs/katello/3.11.yaml matches expectations

On Branch Date

Release Owner

  • Create KATELLO-3.11 branches

  • Bump versions to 3.12-master

  • Branch docs

    • Use ./tools branch-docs config/katello/3.11.yaml to branch automatically or by hand:
    • Draft release notes in markdown (example), with these sections (and do not use personal pronouns):
      • Headline features: half a dozen important features with a few sentences description each
      • Upgrade notes: all important notices that users must be aware of before upgrading
      • Release notes: bullet point list by category of most changes, excluding bug fixes for issues introduced during the release cycle, include link to bug numbers. You can auto-generate changes using the ‘changelog’ command in tool_belt

  • Update API docs and open a PR with the changes:

    VERSION=
GITDIR=~/git  #directory containing theforeman.org git repo

FOREMAN_APIPIE_LANGS=en rake apipie:cache
cp -rf public/apipie-cache $GITDIR/theforeman.org/plugins/katello/$VERSION/api
# clear out json files
find $GITDIR/theforeman.org/plugins/katello/$VERSION/api -name "*.json" -type f -delete

cd $GITDIR/theforeman.org/
cp plugins/katello/nightly/api/index.md  $GITDIR/theforeman.org/plugins/katello/$VERSION/api/
sed -i "s/version: nightly/version: $VERSION/g" $GITDIR/theforeman.org/plugins/katello/$VERSION/api/index.md

cp -rf $GITDIR/theforeman.org/api/new_version_template/apidoc/* $GITDIR/theforeman.org/plugins/katello/$VERSION/api/apidoc

Release Packager

  • Generate a release GPG key

  • Run ./tools koji configs/katello/3.11.yaml from tool_belt to create Koji tags

  • Run ./tools mash-scripts configs/katello/3.11.yaml from tool_belt to create Koji mash scripts and open PR to tool_belt to commit

  • Copy mash scripts to Koji

  • Create new mash script on Koji

  • Create an install and upgrade pipeline playbook in forklift and open PR

  • Add 3.11 to Forklift versions config

  • Add new Katello release job to foreman-infra

  • Update Katello PR pipeline with new version pipeline

  • Ensure releases of installer modules, this is typically done as part of Foreman module release workflow

1 Like