Apologies for the late notes.
Present: @upadhyeammit (chair), @ekohl (notes), @pcreech, @Zhunting, @iballou
Foreman 3.2
- Feature #34505: Add hammer-cli-foreman-host-reports to the installer - Installer - Foreman is blocked on Debian packaging
- Feature #34126: Deliver EL8 repositories as modular repositories to fix dependency resolution, get automatic dependent module enablement and handle dependency resolution without module_hotfixes - Packaging - Foreman at risk, @ekohl will update the issue with the current status
- Cherry picks: look ok
- Decided to go ahead with the GA on the 15th
- Debian plugin pipeline is failing, should be looked into
Foreman 3.0
- Just merged fix thor bundling also for bionic and focal by evgeni · Pull Request #7677 · theforeman/foreman-packaging · GitHub, pipelines will be kicked
Katello 4.4
- Upgrade pipeline failed for an unrelated reason, should proceed
Other
Switch Katello repositories to be numbered based on the Foreman version
Currently the Katello repositories use Katello versioning (see Index of /katello). This means users need to map some Katello version to some Foreman version. It also means that in Foreman’s branching process the packaging we can’t simply replace nightly with 3.3, but need to look for each one if it needs to be 3.3 (Foreman) or 4.5 (Katello). Th
e proposal is to get everything aligned on a single standard.
One suggestion is to bump both Foreman and Katello to a common number (5.0), but there’s no concensus and no decision.
Gating nightly publishing of Foreman and Katello only if both Foreman and Katello pipelines are green
There is an open RFC for this:
Other agenda items postponed to a later meeting