Meeting Type: Foreman Release Team Meeting
Date: Jul 15, 2026
Community: https://community.theforeman.org
Foreman Nightly
- nightly is
- openssl workarounds were reverted, new openssl is
Foreman OCI Releases
- We discovered that we need new nightly tags
- Odilon is going to start working on stage → prod gating job
- We now rebuild images every time katello-nightly-rpm pipeline passes
Foreman 3.19
- Status Updates
- Foreman 3.19.1 is the latest release
Foreman 3.18
- Status Updates
- CI is green
- Foreman 3.18.2 is the latest release
Katello 4.21
- Status Updates
- Katello 4.21.0 is released
Katello 4.20
- Status Updates
- 4.20.1 is out Katello 4.20.1 is now available
- 4.20.2 is in discussion, we’ll release if needed, but it’s less likely to happen
Pulp Integration
- Current Status
- We start building EL10 pulpcore this week
- We’ll need to take a look at the Puppet modules to see if they can install Pulp on EL10
- PR to remove obsolete packages: Remove obsolete packages for EL10 transition by zjhuntin · Pull Request #2751 · theforeman/pulpcore-packaging · GitHub
- We start building EL10 pulpcore this week
Other
- How do we identify patches to be cherry-picked to stable branches?
- There is currently no standardized process for this in Foreman core. Katello runs triage meetings to review community-reported issues.
- There might be an expectation that the Foreman Release Owner identifies patches to be backported. But the Release Owner has no clue about what needs to be backported if they are not taking an active part in Foreman core development.
- Odilon likes the PR labels approach - flag issues to be backported using PR labels - and suggested using the GitHub milestones feature
- [UPDATE] Improving the Foreman backporting process was raised in the community forum by Ian to discuss the backporting process