On Tue, Nov 10, 2026 at 08:22:34PM +0000, Christopher Baines wrote: > I don't know where this coupling of branches and teams has come from, > the package graph is far more important in my mind, and at the moment > that isn't structured around "teams" (although we can move in that > direction).
The reason I am advocating for team branches is that responsibility and agency come together. I am still traumatised by the previous core-updates branch! There random people pushed random commits (slightly exaggerating of course). Once something broke, nobody was really responsible. With an xxx-team branch, it is clear that the xxx team is expected to work together to get the branch through. But we can always try something else. The world-rebuild branches are/were such a trial. The way they were carried out, they depended a lot on an individual, so I am not sure they could completely replace team branches. Maybe we could try more things. And more efforts to disentangle the dependency graph would also be helpful. Maybe not everything needs to depend on python, rust and several llvm versions; sometimes a small change could be enough to reduce the number of dependents by thousands (as a recent PR of yours shows, Chris). Andreas
