Hi Florian, On Thu, Jan 26, 2023 at 06:41:27PM +0100, Florian Bezdeka wrote: > From the CIP projects perspective we would like to improve the > situation. > > From my perspective the following could be done: > > - Instead of (or in addition to) building and testing released -rt > branches enable testing of -rt release candidates > - Make sure the build results get back to the maintainers > > I'm not sure if every -rt branch has a -rc branch. I'm not familiar > with the -rt release process yet. The process so far is, that every stable maintainer updates his tree (merges the stable tree) and does a local build and local tests. Usually when merging latest upstream stable release there are no or little fallouts. When the maintainer is happy he does the release by pushing the changes to the usptream branch. The release candiates come only into play when there is something the maintainer is not sure how to handle or -rt patches are backported which need some more eyes to look on. That means Sebastian's approval :) IIRC, I did give a presentation on the workflow some time ago... https://lpc.events/event/4/contributions/293/attachments/237/416/maintaining-out-of-tree-patches-over-the-long-term.pdf https://www.youtube.com/watch?v=2ab4Knwlmo4 When we started with this process kernelci didn't build these branches but that is long time ago. Personally, I don't mind doing an official -rc for every release and getting some additional builds and tests run by kernelci. Though just piping the results back is the easy thing, the time consuming task is to fix those problems. Do you plan to help out here? Thanks, Daniel
