Foreman
- Nightly builds failure.
- 3.2(To Do )
- Status of installer module releases
Katello
- 4.4
Present: @upadhyeammit (chair), @ekohl (notes), @evgeni, @iballou
Previous meeting
Notes from last time were approved.
Foreman
Nightly
- Network failure in Debian nightly. What can we do? Not a lot. For now we accept that sometimes this fails.
- There was a failure with modularity but the fix was merged this morning.
3.2
- Installer modules haven’t been released. Some CI failures due to the modularity changes in nightly. @wbclark is the assigned installer maintainer but he’s busy so @ekohl might take over the releases.
- TODO
- Feature #34325: enable redis cache for pulp content server by default - Installer - Foreman Should be ready to merge. CI restarted this morning, haven’t checked back.
- Bug #34189: Candlepin errors when using an encrypted key generated with genpkey or on a FIPS enabled machine - Installer - Foreman Ran into the aforementioned nightly CI issues, @ekohl will continue to work on this.
- Bug #33948: New host detail page shows IP address over multiple lines - Foreman Need to check with @amirfefer if this hasn’t been solved already
- Refactor #33781: Deprecate other than DSL setting definitions - Foreman Pinged @ezr-ondrej to see if this should go in. It looks ready.
- Feature #33444: Drop old Debian signing key in Foreman 3.2 - Foreman @evgeni will check what needs to happen exactly. Won’t be a blocker to 3.2
Katello
4.4
- The PR to tool_belt has been submitted, pending review on the packaging team if the tags are correct
- Triage today. There it will be determined what goes in the release and what’s pushed out to the next.
Other
The question is raised how we align GitHub pull requests to releases.
For plugins there really isn’t any. It’s up to plugin maintainers. Technically we allow major version bumps in stable releases, as long as the plugin maintainers feel comfortable with it (installer compatibility could be an issue to consider). The solution here is to work with maintainers to get them to understand.
Regarding core alignment: today we use Redmine and the versions there. This allows us to follow it and cherry pick where needed. It is interesting to know that recently Pulp switched from Redmine to using only GitHub. It would be worthwhile to find out what their experiences are and what we can learn. There are also hybrids like syncing Redmine versions to GitHub milestones.
In the short term we can start with describing the current situation. Today that knowledge is mostly tribal knowledge but it would be good if it’s written down. @upadhyeammit will work on this.
I’ve started using Github milestones in ForemanPuppet to guide versioning, but it is not as flexible as Redmine. I’d consider it a blocker, but I just might not understand how to use it properly 