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

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 63713 in the body.
You can then email your comments to 63713 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Christopher Baines <mail <at> cbaines.net>
To: guix-patches <at> gnu.org
Subject: Request for merging "ruby-team" branch
Date: Thu, 25 May 2023 08:59:31 +0100

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

I'm getting a bit ahead of myself here as I've only just created the
branch, but I'm creating this issue mostly so that I can write and test
qa-frontpage code for finding and processing these "Request for merging"
issues.

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

Message #10 received at 63713 <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludo <at> gnu.org>
To: Christopher Baines <mail <at> cbaines.net>
Cc: 63713 <at> debbugs.gnu.org
Subject: Re: bug#63713: Request for merging "ruby-team" branch
Date: Thu, 08 Jun 2023 23:00:31 +0200

Christopher Baines <mail <at> cbaines.net> skribis:

> I'm getting a bit ahead of myself here as I've only just created the
> branch, but I'm creating this issue mostly so that I can write and test
> qa-frontpage code for finding and processing these "Request for merging"
> issues.

Hi!  So did it process it?  :-)

Ludo’.

Message #13 received at 63713 <at> debbugs.gnu.org (full text, mbox):

From: Andreas Enge <andreas <at> enge.fr>
To: 63713 <at> debbugs.gnu.org
Subject: Processing
Date: Fri, 9 Jun 2023 15:00:55 +0200

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.

Andreas

Message #16 received at 63713 <at> debbugs.gnu.org (full text, mbox):

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: Re: [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)]

Message #19 received at 63713 <at> debbugs.gnu.org (full text, mbox):

From: Christopher Baines <mail <at> cbaines.net>
To: 63713 <at> debbugs.gnu.org
Subject: Re: [bug#63713] Request for merging "ruby-team" branch
Date: Mon, 03 Jul 2023 12:38:43 +0100

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

Christopher Baines <mail <at> cbaines.net> writes:

> I'm getting a bit ahead of myself here as I've only just created the
> branch, but I'm creating this issue mostly so that I can write and
> test qa-frontpage code for finding and processing these "Request for
> merging" issues.

I'd like to merge ruby-team this week, I think it's pretty much ready.

There are a few breakages, I'm going to try and make some improvements
to the qa-frontpage to more easily highlight these.

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

Message #24 received at 63713-done <at> debbugs.gnu.org (full text, mbox):

From: Christopher Baines <mail <at> cbaines.net>
To: 63713-done <at> debbugs.gnu.org
Subject: Re: [bug#63713] Request for merging "ruby-team" branch
Date: Mon, 10 Jul 2023 08:28:45 +0100

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

Christopher Baines <mail <at> cbaines.net> writes:

> Christopher Baines <mail <at> cbaines.net> writes:
>
>> I'm getting a bit ahead of myself here as I've only just created the
>> branch, but I'm creating this issue mostly so that I can write and
>> test qa-frontpage code for finding and processing these "Request for
>> merging" issues.
>
> I'd like to merge ruby-team this week, I think it's pretty much ready.
>
> There are a few breakages, I'm going to try and make some improvements
> to the qa-frontpage to more easily highlight these.

I've pushed the ruby-team changes to master now as
2ccf3eb495eafe4c825a568697dea2630addeeaa.

[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.