Foreman 3.9.0-rc3 release process

Make this post a wiki (help)


Preparing code: 2023-12-05

Installer Maintainer

  • Make patch releases of installer modules that have important changes
    • Branch to MAJ.MIN-stable if recent changes to the module aren’t suitable for patch (x.y.z) release

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.9.0-rc3 in redmine. issues can be used to generate a comparison between the two.

Tagging a release: 2023-12-05

Release Owner

Release Engineer

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: 2023-12-05

Release Engineer

Background documentation

Manual updates: 2023-12-05

Release Owner

After the packages have been released

Release Owner

[evgeni@web01 ~]$ ls /var/www/vhosts/yum/htdocs/releases/3.9/el8/x86_64/foreman-release* -alh
-rw-r--r--. 1 yumrepo yumrepo 14K Dec  6 16:41 /var/www/vhosts/yum/htdocs/releases/3.9/el8/x86_64/foreman-release-3.9.0-0.2.rc2.el8.noarch.rpm
-rw-r--r--. 1 yumrepo yumrepo 14K Dec  6 16:41 /var/www/vhosts/yum/htdocs/releases/3.9/el8/x86_64/foreman-release-3.9.0-0.2.rc3.el8.noarch.rpm
lrwxrwxrwx. 1 yumrepo yumrepo  44 Dec  8 18:40 /var/www/vhosts/yum/htdocs/releases/3.9/el8/x86_64/foreman-release.rpm -> foreman-release-3.9.0-0.2.rc2.el8.noarch.rpm

@ehelms seems the “keep dates correctly” thing is still broken and breaks the “latest” symlink :confused: