Re: Branch (and team?) for mesa updates

[Andreas Enge]

Hello,

Am Mon, Jun 19, 2023 at 06:25:04PM +0000 schrieb John Kehayias:
> Master can be merged into this branch just prior to a patches going to this 
> branch with the expectation merging back to master will be soon after and 
> changes are only affecting packages that won't be touched on master anyway. I 
> think this should be relatively clean and straightforward, a good use of our 
> new branching/building strategy.

I am a bit wary of branches just sitting around; after a while we will
forget whether a branch still needs merging, or is just a placeholder.
So I would suggest to delete every branch right after merging, and then
branch off of master later when a new patch is going to be applied.
This will also create a cleaner history by avoiding a merge.

This is compatible with how cuirass works. We can keep the mesa-updates job,
and when the branch does not exist, it will just do nothing. You just need
to be sure to use the same branch name again next time, and it should be
picked up by the cuirass job.

Andreas