- Pending installer module releases.
- According to the schedule, we have completed the stabilization week and still have a few days before branching. If all of the tasks required have been completed, we may be able to branch before the scheduled date of February 10th. This can allow us target RC1 this week.
- Release 3.1.2?
- 3 modules remaining, PRs open for all of them. There is 1 open question, but it otherwise proceed without it.
- We should be all set. The 3.2.0 TODO is nearly empty. Only Bug #33948: New host detail page shows IP address over multiple lines - Foreman remains but that’s not blocking for branching.
- One concerning thing is common Katello and Luna nightly pipeline failures (Katello-nightly-rpm-pipeline 1220 failed and luna-nightly-rpm-pipeline 332 failed for example). @Justin_Sherrill and @ekohl will sync after the meeting.
- @Zhunting is creating the GPG key for the release.
- Updates will be sent to Foreman 3.2 branching process
- Call for maintainers to nominate issues. Discussion on exact planning next Monday.
- @iballou has been bumping issues to determine what needs to get in and what gets bumped.
- @Zhunting will review the Koji tags in the tool_belt PR
- Updates will be sent to Katello 4.4 Branching Process
Proposal by @Justin_Sherrill: change the nightly pipeline to block on plugins
This was a fairly long discussion and @Justin_Sherrill will submit a separate RFC with more details. The problem description is roughly that the katello pipeline fails quite often while Foreman’s pipeline doesn’t. Partly this is because Katello has more tests so more can fail. In practice this means Foreman gets promoted while Katello doesn’t and the repositories get out of sync. Ideally speaking there wouldn’t be such a strong coupling between the two, but in practice there is. For example, the installer is built in the Foreman repository but includes code for Katello.
The proposal is to start gating Foreman’s pipeline on Katello.
Ewoud notes this creates a hard dependency on Katello to release, which could place a burden on non-Katello developers. The conclusion is that we agree these problems exist, but the solution is not so obvious. Justin will submit an RFC and move the discussion there.