Release Team Meeting 2026-07-22

ogajduse · July 22, 2026, 1:00pm

Meeting Type: Foreman Release Team Meeting
Date: Jul 22, 2026
Community: https://community.theforeman.org

Foreman Nightly

nightly is except pulpcore-nightly-rpm-pipeline and foreman-nightly-rpm-pipeline which failed with 502 Bad Gateway on COPR. – Retriggered
Foreman 5.0 prep week starts next week; we’ll publish Foreman 5.0 and Katello 5.0 release procedures this week
@iballou to reach out to foremanctl maintainers about if and how we need to adjust the release process to handle foremanctl correctly.

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

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

ogajduse · July 23, 2026, 10:11am

5.0 branching & release procedures created:
Foreman:

Katello: