Foreman 3.3 branching process

Development Releases
1

Make this post a wiki

Roles

Prep Week: 2022-04-25 to 2022-04-29

Installer Maintainer

Release Owner

  • Ensure headline features planned for the release have been merged or push them off to the next release.
  • Translations:
    • Update locales in foreman develop: make -C locale tx-update
    • Ask plugin authors to start extracting i18n strings and pushing the changes into develop/master git branches so Transiflex can pick it up
    • Announce string freeze date on discourse and send announcement via Foreman localization
    • Update foreman-dev with translations status to encourage 100% translations before release

Stabilization Week: 2022-05-02 to 2022-05-06

Release Owner

Release Engineer

  • Create new GPG key for release. See GPG_Keys if needed.
  • Publish the key by exporting the GPG key
  • Create new settings files for client, ensure it has the rights OSES list and commit it too.
  • Create configs/foreman/3.3.yaml based on the nightly and previous release. Ensure that any based_on entries are filled out and pointing to nightly version of tag.
    • Generate mash configs
      bundle exec ./tools.rb mash-scripts configs/foreman/3.3.yaml
sed -i '/strict_keys/ s/True/False/' mash_scripts/foreman/3.3.0/foreman-plugins-3.3-*.mash
    • Open PR with new config and mash scripts for review
    • Create mash configuration on Koji, from tool_belt checkout:
      scp mash_scripts/foreman/3.3.0/*.mash root@koji.katello.org:/etc/mash/
  • Update mash script if needed - collection-mash-split.py
  • Add the new release to the JJB job definitions in jenkins-jobs
    • Create a 3.3.groovy in pipelines/vars/foreman/ describing the operating systems the release supports
    • Add 3.3 to the version list in theforeman.org/yaml/includes/foreman_versions.yaml.inc
    • Add 3.3 to the version list in centos.org/jobs/foreman-pipelines.yml
    • Create test_3_3_stable.yaml and test_proxy_3_3_stable.yaml in yaml/jobs/
  • Open PR to remove any jobs that are related to end of life versions
  • Open PR to add 3.3 to Forklift versions config. Once the PR is merged, upgrade pipelines will fail, so do not merge it before packaging has been branched.

Branching: 2022-05-10

Release Engineer

  • Branch RPM packaging using tool_belt
    • Clone tags and create build targets in Koji: bundle exec ./tools.rb koji --commit configs/foreman/3.3.yaml
    • Create a rpm/3.3 branch in foreman-packaging based on rpm/develop
  • Branch Debian packaging

Release Owner

The next step should only be done after all branching, including packaging, has completed.

Preparing build systems: 2022-05-10

Release engineer

  • Update foreman-packaging rpm/develop to ensure nightlies build:
    • rpm/develop:
      • Update the build tag: sed -i 's/fm3_3/fm3_4/g' rel-eng/{releasers.conf,tito.props} package_manifest.yaml
      • Set to version 3.4.0, reset release to 1 in packages/foreman/foreman{,-{installer,proxy,release,selinux}}/*.spec and packages/foreman/rubygem-hammer_cli{,_foreman}/*.spec. Then create a changelog using obal changelog --message '- Bump version to 3.4-develop' foreman{,-{installer,proxy,release,selinux}} rubygem-hammer_cli{,_foreman}
    • deb/develop: scripts/changelog.rb -v 3.4.0-1 -m "Bump changelog to 3.4.0 to match VERSION" debian/*/*/changelog
  • Prepare build systems for 3.3 release:
    • foreman-packaging’s rpm/3.3
      • Update packages/foreman/foreman-release/foreman.gpg, mock/*.cfg, package_manifest.yaml, rel-eng/{releasers.conf,tito.props} and repoclosure/*.conf
  • Trigger the foreman-packaging-rpm-3.3 job once, so that GitHub hooks are properly set up.
  • Trigger the foreman-packaging-deb-3.3 job once, so that GitHub hooks are properly set up.

Other systems: 2022-05-10

Release Owner

  • Create release schedule page for next version (3.4) linked from Development_Resources and post planned schedule on Discourse.
  • Create Redmine versions
    • Add next version number (3.4.0) and make sure it is shared with subprojects in foreman
    • Add first patch release (3.3.1) and make sure it is shared with subprojects in foreman
  • Ensure current Foreman deprecations for the next release are removed in develop

This was based on the wiki procedure and sometimes has a bit more info.

2

FTR, there were some bugs in the new MQTT feature of puppet-foreman_proxy, but they got sorted by now, and luna-nightly-rpm-pipeline [Jenkins] is passing again.

I did all required module releases, and we’re good to go on that part.

1 Like
3

And just because I said they are sorted, it didn’t mean they were really sorted (quite literally, actually).

We’ll have to pick ensure config notifies mosquitto by evgeni · Pull Request #758 · theforeman/puppet-foreman_proxy · GitHub into 3.3 (I’ll take care of that tomorrow, just raising here fore awareness)

4

Also, it seems RPM package branches were not created properly:

cc @packaging