From: Simon Tournier <zimon.toutoune@gmail.com>
To: Vagrant Cascadian <vagrant@debian.org>,
Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: Christopher Baines <mail@cbaines.net>, guix-devel@gnu.org
Subject: Re: Process for reviewing patches as someone without commit access
Date: Thu, 07 Sep 2023 21:05:20 +0200 [thread overview]
Message-ID: <86r0n9ajnz.fsf@gmail.com> (raw)
In-Reply-To: <87v8cmklbp.fsf@wireframe>
Hi,
There are only two hard things in Computer Science…
On Thu, 07 Sep 2023 at 09:19, Vagrant Cascadian <vagrant@debian.org> wrote:
>>> Discussing about idea, would it be possible that the QA infrastructure
>>> automatically send a message to Debbugs for tagging? For example, the
>>> usertag ’qa-ok’ or whatever other meaningful name. :-)
>>
>> +1 for that as well, maybe 'qa-passed'.
…naming and…
> The only concern is that it is maintaining QA information in multiple
> places, the QA service itself, and trying to mirror it to the bug
> tracker...
…cache invalidation. :-)
> QA might fail with a later patch iterations, so it should also then go
> and remove the qa-passed tag? Should it remove the tag when QA is
> currently in an unknown state?
That’s good questions. Yeah, maybe QA could check when starting to
build that there is no ’qa-passed’ or remove it if any.
Cheers,
simon
next prev parent reply other threads:[~2023-09-09 9:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-06 15:55 Process for reviewing patches as someone without commit access Christopher Baines
2023-09-06 18:17 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-09-06 18:19 ` Christopher Baines
2023-09-06 19:01 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-09-06 23:37 ` Simon Tournier
2023-09-06 23:59 ` Simon Tournier
2023-09-07 2:47 ` Maxim Cournoyer
2023-09-07 9:55 ` Simon Tournier
2023-09-07 16:19 ` Vagrant Cascadian
2023-09-07 19:05 ` Simon Tournier [this message]
2023-09-27 11:58 ` Christopher Baines
2023-10-04 15:46 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86r0n9ajnz.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=guix-devel@gnu.org \
--cc=mail@cbaines.net \
--cc=maxim.cournoyer@gmail.com \
--cc=vagrant@debian.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).