Am Mon, Apr 13, 2026 at 05:41:51PM +0200 schrieb Gabriel Wicki: > IMHO this would be the preferred option! I see that there is a subsection > in the reference manual (Managing Patches and Branches)—unfortunately it > is inside the somewhat outdated `Tracking Bugs and Changes' section and > could maybe itself be a bit sharpened in some parts? I'll gladly help > bringing this section up-to-date and moving it(?) so it is not hidden > within the more outdated parts
In particular, QA should be changed to not rely on debbugs anymore... > > I think a bit more proactivity would be needed to make the baton passing > > smoother and faster, like the team first in line could already exchange > > with the next one about their plans and timeline. > YES. But maybe we could use some responsibility information on the QA > queue—for the cases like the `misc-world-rebuild` branch (opened for > https://codeberg.org/guix/guix/pulls/5312) so people could coordinate > more easily? WDYT? Almost all branches are related to teams, so their information is readily available. misc-world-rebuild is an exception, but I think it has been announced on guix-devel, which committers (and team members?) are expected to follow, there is even a GCD talking about it ;-) For "update-sbcl-to-2.6.3" we have made a mistake, it should have been called "lisp-team", and everything would have been clear. Andreas
