Hello, there is a general problem of us having many world rebuild branches, and not enough build power to handle them quickly (plus occasional interruptions of the tools, like when we upgraded bayfront).
Am Fri, May 22, 2026 at 11:52:52AM +0200 schrieb Ricardo Wurmus: > with our (necessary) practice of serializing branch merges in a queue I've > been waiting for over a month to get R updates merged. Currently, the r-team > branch is 6th in line, and it has grown to about 900 commits. > > I've been adding updates on the r-team branch for weeks, and I'll continue > to do this until I go away from computers from June 16 until at least the > end of October. But I wonder if we could not find a "social solution" in this case? I think python-team can be merged; misc-world-rebuild has trouble being evaluated on QA, so I am afraid it will not be ready any time soon, and the following branches will take precedence; update-sbcl-to-2.6.3 has been waiting for a long time already and should be quite small, so it would be nice to get it through just after python-team; haskell-team is a bit experimental, the team has no committers and I am volunteering to try to shepherd it through; it can certainly be postponed a bit; maybe audio-team can also be postponed, to make room for r-team that usually builds without problems and becomes a bit more urgent since you announced your leave for a somewhat longer time? So I am suggesting the reordering python - sbcl - r - world - haskell - audio. Would that be okay with the branch shepherds? Andreas
