Ludovic Courtès <l...@gnu.org> writes: > Christopher Baines <m...@cbaines.net> skribis: > >>> But we also need more flexibility, in particular the ability to say >>> “this branch is ready so it should be merged now”. Could we provide a >>> way to change the order of branches shown by qa.guix.gnu.org? >> >> The current mechanism to do this is mentioned on [1], but this probably >> needs to be mentioned on the qa-frontpage as well. >> >> 1: >> https://guix.gnu.org/manual/devel/en/html_node/Managing-Patches-and-Branches.html > > Oh, my bad; so each person/group responsible for a branch can right away > mark it as blocked by ‘r-team’ <https://issues.guix.gnu.org/76303>, and > then ‘r-team’ will be at the top of the list and QA will pick it up. > > Did I get that right?
Yep, pretty much, but I think anyone can do this, the guidance in the docs is that there just needs to be some discussion/agreement. My hope is that node-team can be pushed to master within the next few days so I would hope that just blocking qt-team and tex-team by r-team should bump it up enough to be worked on by QA next week.
signature.asc
Description: PGP signature
