Release Team Meeting 2024-08-28

Development Releases
1

Foreman 3.12

3.12.0 Schedule | 3.12 Branching Process

  • RC2 state
    • some desire for an earlier RC2 if feasible

Foreman 3.11

3.11.2 TODO | 3.11.2 DONE | CI Overview

Foreman 3.10

3.10.1 TODO | 3.10.1 DONE | CI Overview

Katello 4.14

4.14 Branching

  • 4.14 RC1 public
    • Issue with pulpcore repo pointing to nightly
    • Centos 9 Upgrade issue - Chose to accept as known issue for now

Katello 4.13

  • 4.13.1 Released

Katello 4.12

Pulp

2

Meeting summary:

Mostly chatted about a hope for some upstream mid-rc artifacts to help with some needs for testing some fixes early.

Katello offered a RC1.1 with latest available cherrypicks. Foreman doesn’t have capacity.

RC2 schedule is unchanged.

Discussion around documentation PRs that are outstanding.

Post-meeting, it was brought up on matrix about the need for a foreman 3.10 and 3.11. Discussion around that still happening as it is important to get a timely 3.10 and 3.11 out.

1 Like
3

I would avoid doing “minor” versions in RCs. So don’t name it RC1.1 but just name it RC2. The schedule says just RC 1 and 2, but there’s no reason you can’t change it and create RC2 this week and do RC 3 next week.

The purpose of RCs is that you want to get feedback. If you feel you need to release more code to get better feedback earlier, by all means do an additional one.

1 Like