Release team meeting 2023-03-08

[ekohl]

Last week @ekohl was on PTO and forgot to notify others.

Present: @ekohl (chair, notes), @lfu, @Zhunting, @Odilhao

Foreman 3.7

• @ekohl to post the schedule, as part of branching procedure

Foreman 3.6

• RC2 needs to be released for Katello to proceed. @ekohl will post the procedure

Foreman 3.5

• 3.5.2 process was posted (Foreman 3.5.2 release process) and should have been released by now, but has been delayed.

Katello 4.9

No news

Katello 4.8

• RC1 blocked on Foreman RC2 to include update theforeman/pulpcore to 7.2.0 · theforeman/foreman-installer@2fff409 · GitHub
• Add Katello 4.8 api docs by lfu · Pull Request #16 · theforeman/apidocs · GitHub was created, @ekohl will review
• The branching procedure has steps in the documentation. Those were unclear to @lfu and @ekohl will review and recommend steps moving forward.

Katello 4.7

No updates

[ekohl]

@lfu you asked me about the docs and it took me a while to get back to it. I’ll start with what needs to be done, then we can figure out in which process it belongs.

We want to fill in guides/doc-Release_Notes/topics/katello.adoc in foreman-documentation. For nightly that’s foreman-documentation/katello.adoc at master · theforeman/foreman-documentation · GitHub. Ideally we actually do this while developing Katello in nightly. Then on branching you only need to clean it in nightly post-branching.

The branching actually happens in the Foreman process, so I think we should keep that in Foreman’s branching process, rather than split it up. So my recommendation is to drop it from Katello’s branching process. For Katello I’d recommend checking katello.adoc as part of every release, thus moving it to the release procedure.

I’ve opened Correct Katello's procedures around docs by ekohl · Pull Request #511 · theforeman/tool_belt · GitHub to formalize that.