Foreman 3.6.0-rc1 release process

[ekohl]

Make this post a wiki

Roles

• Release Owner: @ekohl
• Release Engineer: @ekohl

Manual updates: 2022-02-23

Release Owner

• Update manual if applicable for any additional installation steps
• Update the website’s release notes section in the manual
  • Using the release notes script: ./scripts/release_notes.rb foreman 3.6.0
  • Append CLI release notes taken from the hammer-cli and hammer-cli-foreman changelogs, in theforeman.org and docs.theforeman.org websites release notes.
  • Headline features: half a dozen important features with a few sentences description each
  • Upgrade warnings: all important notices that users must be aware of before upgrading
  • Deprecations: anything that will be removed in a future release
  • Submit this as a PR
• Update docs.theforeman.org
  • Using redmine_release_notes script (see README as well): ./guides/doc-Release_Notes/redmine_release_notes foreman 3.6.0 > ./guides/doc-Release_Notes/topics/foreman-3.6.0.adoc
  • Append CLI release notes taken from the hammer-cli and hammer-cli-foreman changelogs to foreman-3.6.0.adoc.
  • Add topics/foreman-3.6.0.adoc to guides/doc-Release_Notes/master.adoc: sed -i '/x.y.z releases here/a include::topics/foreman-3.6.0.adoc[leveloffset=+1]' guides/doc-Release_Notes/master.adoc
  • Make sure foreman-contributors.adoc is updated
  • Make sure headline features, upgrade warnings and deprecations are in sync with the website
  • Submit this as a PR
• Generate the apipie docs and raise pull request in apidocs repository

Preparing code: 2022-02-23

Release Owner

• Remove/change target version field for any open Redmine tickets assigned to the release still (next minor, unset it or reject)
• Ensure that code in git matches issues fixed in 3.6.0-rc1 in redmine. issues.rb can be used to generate a comparison between the two.

Tagging a release: 2022-02-23

Release Owner

• Make sure test_3_6_stable and smart-proxy3.6-stable-test are green using verify_green_jobs
• Run make -C locale tx-update in foreman 3.6-stable
• Tag the projects
  • Create tags tag_project
  • Push tags tag_push
• Run the Jenkins Tarballs Release using release_tarballs to create tarballs

Release Engineer

• Sign Tarballs
  • Download
  • Inspect
  • Sign and upload detached signatures

Note: If for some reason there was an issue with the tarballs that required uploading new tarballs, CDN cache should be invalidated so that the builders use the updated tarballs.

Packaging a release: 2022-02-23

Release Engineer

Background documentation

• Update foreman-packaging branches
  • rpm/3.6
  • deb/3.6
• Wait for packages to be built
  • rpm/3.6
  • deb/3.6
• Check for outstanding PRs against 3.6 packaging, and merge if possible:
  • rpm/3.6
  • deb/3.6
• Sign the RPMs in the release
  • Download
  • Sign
  • Upload RPM signatures
  • Upload RPMs
• Sign RPMs for client repos (call scripts with PROJECT=client)
  • Download
  • Sign
  • Upload RPM signatures
  • Upload RPMs
• Kick off the release pipeline by calling release_pipeline
• Kick off the client pipeline by calling PROJECT=client release_pipeline
• Kick off the plugins pipeline by calling plugins_pipeline

After the packages have been released

Release Owner

• Update installer options section using the get-params script (Note: this step can only be done after packages are released)
• Add the 3.6 in foreman_versions list in website’s _config.yml file
• Announce the release on Discourse
• Update the topic in #theforeman channel on Libera.Chat
• Share the release announcement on Twitter
• Release pipeline will trigger foreman-plugins-3.6-deb-test-pipeline and foreman-plugins-3.6-rpm-test-pipeline. These don’t block releases but can be used to understand known issues around plugin compatibility with Foreman 3.6.

[ekohl]

Last week I already kicked off the first release, but it didn’t have released versions of Hammer. Once foreman-3.6-release-pipeline #2 [Jenkins] completes that should be resolved.