Present: @ekohl (chair/notes), @iballou, @Zhunting, @pcreech, @cintrix84, @lfu, @Griffin-Sullivan
Introductions
@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 https://community.theforeman.org/c/development/releases/20. 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
- Branch process posted: Foreman 3.7 branching process
- In installer module release week
- @ekohl is preparing module releases; Foreman landscape now has CI badges to help to determine stability
- Translation plugin DSL: Fixes #36331 - Expose translation registration in plugin DSL by adamruzicka · Pull Request #9692 · theforeman/foreman · GitHub is about to be merged and may require modifications in plugins to utilize this.
Foreman 3.6
- No updates
Foreman 3.5
- No updates
Katello 4.9
- Branching process posted: Katello 4.9 branching process
- Add Katello compatibility to tool_belt config generation by ekohl · Pull Request #214 · theforeman/theforeman-rel-eng · GitHub
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.