Release team meeting 2023-05-10

Present: @ekohl (chair/notes), @iballou, @Zhunting, @pcreech, @cintrix84, @lfu, @Griffin-Sullivan


@Griffin-Sullivan has shown an interest in helping with release work. @ekohl gave a short introduction about release work.

The best starting place is: GitHub - theforeman/theforeman-rel-eng: Release engineering scripts

Besides that we have a weekly meeting to sync up on status, which are posted on There we also post the release schedules.

Foreman always has two supported releases (currently 3.5 & 3.6) and one in development (currently 3.7). Once 3.7 is released, 3.5 will be end of life (EOL). Releases are on a 3 months schedule, with roughly 3 months between each branching date. See schedule for the script that generates the template.

Foreman 3.7

Foreman 3.6

  • No updates

Foreman 3.5

  • No updates

Katello 4.9

Katello 4.8

  • No updates

Katello 4.7

  • 4.7.5 release process posted: Katello 4.7.5 Release Process
  • Waiting on release engineering to update. Perhaps we can move this task to the release owner in the future: Use (or expand bump_rpm_packaging to submit a PR to foreman-packaging. Then the release engineer can just merge it and sign the resulting package.
1 Like