Hello again, I understand the frustration at our progress in branch merging being so slow that systems like R, for instance, are already outdated when they are finally merged.
Am Fri, Apr 11, 2025 at 05:27:05PM +0200 schrieb Andreas Enge: > Well, there *is* flexibility. If the r-team branch is ready and built > out on CI, say, you can merge it now (well, it would be annoying if it > were merged right before a different branch that is also ready and at > the top of the queue on QA, so a bit of coordination would be needed in > any case). So elaborating on this: Thanks to Chris's work described in https://issues.guix.gnu.org/75894 we expect the node team branch to be merged in the next few days, and hopefully the python-team branch is also close to completion. In any case, QA would pick up the next branch in line. How about profiting from our duplicate build farms by building in parallel r-team on berlin/CI and qt-team and tex-team on bordeaux/QA? Ricardo, I think you have good experience with cuirass to judge whether the r-team branch will be ready for merging. The branches look sufficiently orthogonal in scope that whatever branch is ready first could be merged immediately, as it is unlikely that the combined updates of R and Qt, say, would break many packages that would not already be broken by only one of them. What do you think? Andreas
