Release Team Meeting 2024-11-25

There’s consensus on the schedule, but it still needs to be posted. We’ll aim for 2025-03-18 for GA and work our way back from those dates.
Rails 7 was delayed because Katello nightly hasn’t been green since branching which means it’s hard to test it end-to-end. That in turn needs Foreman 3.12.1 to be released for the EL 9.5 bugfix. There’s also another issue that showed up, for which @iballou created Use newer container naming in container BATS by ianballou · Pull Request #1881 · theforeman/forklift · GitHub.

Foreman 3.13

3.12.1 was all staged on Friday, but release pipeline wasn’t kicked off to avoid releasing on Friday. By now foreman-3.12-release-pipeline #13 [Jenkins] is running and all the release notes have been merged so it’s almost ready to be announced.

While preparing the release procedure @ColeHiggins2 noticed we’ve already released 3.11.4, but no 3.11.5 was created in Redmine. @ekohl has fixed up Redmine and aligned the issues so 3.11.5 is ready to get started. This should also make the Katello 4.15 upgrade pipeline green.

As noticed, nightly has been red since branching. Working on getting that green again.
Fixes #37852 - Support Rails 7.0 by ofedoren · Pull Request #11155 · Katello/katello · GitHub has been reduced in scope and the parts that were pulled out are already merged.

Last week @evgeni pushed out the 4.15 bits without the upgrade pipeline just so the RC was live. Already got the first feedback in Foreman 3.13 release candidate feedback - #2 by lumarel

Still reviewing the linked performance patch
Once a new version is released, that will fail upgrade pipelines because we won’t cherry pick the EL 9.5 fix to Foreman 3.10. We can drop EL 9 from 3.10 by removing these lines: forklift/vagrant/config/versions.yaml at aee3c97f08154c315f1c8db25d239c33a70d1d4f · theforeman/forklift · GitHub