Given this release will be tied to the Foreman 1.20 stream and the
first of it’s kind for Katello, there are a few considerations that
are needed by Katello devs.
Katello PRs currently test against develop, do you want these
switched to test against 1.20-stable branch?
Could we do both?
Foreman PRs are tested against Katello master, there is a
possibility Foreman core may introduce a breaking change in
develop branch before 3.10 is branched
Katello nightly pipelines run against Foreman develop but given
3.10 is against 1.20, do we want to change these for the duration?
The alternatives to the above are to change nothing, hope the time
frame is short enough and post branch test and see if anything is
incompatible with 1.20.
For these two i don’t have great answers, nor think going one way is one
better than another. Ideally we could keep this 3.10 branch working
against both releases, even if we only release against 1.20. I could
see this possibly involving gated checks for the foreman version, which
i would be okay with if we remove them after 1.10 branches. I don’t
know how practical that will be over the course of the month though.
IIUC, the plan is to have 2 katello releases that will be compatible with Foreman 1.20: 3.9, which will come out at the same time as 1.20, and 3.10 which will come out about a month later with some extra features mentioned above. 3.11 will resume releasing in concurrency with foreman (1.21, in that case).