The RC3 is available for testing. Thanks a lot for contributions!
Foreman 2.3.4
The 2.3.4 pipelines finished recently and the release is available. Two issues to be aware of,
The plugins deb test pipeline failed because upgrades are tested from Y-2(2.1) and that broke the ansible plugin. The fresh installs worked without any issue.
Submitted new RC2.1 gem couple of days ago, waiting for feedback on same.
How to decide if Katello needs another RC?
Depends on number of changes done after prior RC. If there are major changes then its recommended to have another RC and get feedback on same from users.
The major changes should be pulled in before stabilization week, uncompleted major changes should be moved to next release before stabilization only. This ensures there aren’t bigger changes in later stage of release.
Latest version in the repositories is still 3.18.2, but I see it was build on koji (and another 3.18.3.1) and redmine has already a 3.18.4. Do we have/had any problem with the pipeline or is there another reason why 3.18.3 is not generally available?
I am asking because I have an environment where I hit some of the bugs and I am not sure if it is an option to take the newer packages from koji.
@Jonathon_Turel@Justin_Sherrill
Is there anything I still need to do with my three PRs to upgrade pulp_deb for Katello 3.18 and proceed with a deb focused 3.18.4 mini release?
Also, I can’t reply to the release announcement for 3.18.3 (presumably permissions). I would appreciate if someone could add a short notice that 3.18.4 is planned for soon after 3.18.3 with a newer Pulp 3 Debian plugin version, and that it is recommended to wait with deb content migrations until then.
Updated the release announcement with a note. I’ll defer to Justin on the pulp specific parts of 3.18.4, but I did notice there is a failure in Jenkins for your Katello PR. I’ll take a look at that for you