Meeting Type: Foreman Release Team Meeting
Date: May 13, 2026
Community: https://community.theforeman.org
Foreman Nightly
- Upgrades are failing, to be resolved by the packaging team
Foreman 3.19
- Status Updates
- Foreman 3.19 was branched, and RC1 is in progress
- Foreman 3.19 RC2 is in two weeks - 2026-05-26
- Foreman 3.20 schedule to be posted in the coming week
Foreman 3.18
- Status Updates
- CI is green
- We expect a release in May(?). Exact date to be posted in the Release Procedure. If there’s a need for 3.18.z, please reach out to @ogajduse.
Foreman 3.17
- Current Release Status
- CI is green
- We expect a release in May(?). Exact date to be posted in the Release Procedure. If there’s a need for 3.17.z, please reach out to @ogajduse.
Katello 4.21
- branching and RC1 in progress
Katello 4.20
- Status Updates
- No releases planned at the moment. We’ll release 4.20.1 next sprint. It will happen in the next couple of weeks.
- Katello folks would like to handle (small) Katello releases within a given X.Y series - Z-streams.
- Release engineers to make sure we have up-to-date procedures in the foreman-rel-eng to reduce ambiguity.
- Katello folks can start anytime they want
Pulp Integration
- Current Status
- Branching 3.105 is done, everything is looking smooth
Other
- [Ian, Zach] Suggested that the future CI failures could be discussed in Infra & CI - TheForeman section. Not only to discuss potential release blockers, as we’ve seen with 3.19 smart-proxy.
- [Ondrej] Will try to move the creation of Foreman and Katello release notes (RN) to GitHub using GitHub Pull Requests. The idea is to open a PR in foreman-documentation, and those who want to contribute to RN would raise a PR against the open PR (branch). Or anyone could simply open a PR against foreman-documentation directly.