GNU bug report logs - #63713
Request for merging "ruby-team" branch

Previous Next

Full log

View this message in rfc822 format

From: Christopher Baines <mail <at> cbaines.net>
To: Andreas Enge <andreas <at> enge.fr>, Ludovic Courtès <ludo <at> gnu.org>
Cc: 63713 <at> debbugs.gnu.org
Subject: [bug#63713] Processing
Date: Fri, 09 Jun 2023 17:31:40 +0100

[Message part 1 (text/plain, inline)]

Andreas Enge <andreas <at> enge.fr> writes:

> It looks so, on
>    https://qa.guix.gnu.org/
> the top two branches, tex-team and ruby-team, are now tagged with the issue
> number. I suppose that also the ordering is not random.

Indeed. There's already some code in the qa-frontpage to look for these
issues and order them, but currently it just uses the date of when the
issue was submitted.

Now that Mumi exposes the blocking information through the GraphQL
endpoint, I need to get the code to use that as well.

I'm not sure if these Ruby changes are what we'll want to merge after
tex-team, maybe tex-team-next or gnome-team are better candidates, but
we can discuss that once tex-team is merged.

[signature.asc (application/pgp-signature, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.