From: Simon Tournier <zimon.toutoune@gmail.com>
To: 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 01:59:33 +0200 [thread overview]
Message-ID: <86sf7qn996.fsf@gmail.com> (raw)
In-Reply-To: <87o7ifb66o.fsf@cbaines.net>
Hi Chris, all,
On Wed, 06 Sep 2023 at 16:55, Christopher Baines <mail@cbaines.net> wrote:
> Once we know what tags to use, I can have the QA frontpage do something
> similar to the "Mark as moreinfo" links, so it's easy to just click a
> button then send the email to change the state of a issue.
That’s cool!
Well, using emacs-debbugs and then
C-u M-x debbugs-gnu-usertags guix-patches RET
the list of usertags is:
guix-patches for-core-updates
guix-patches reviewed-looks-good
And if instead of guix-patches we consider guix then it reads,
guix build-system
guix cross-compilation
guix for-core-updates
guix looks-good
guix patch
guix plz-work
guix powerpc64le-linux
guix ready-to-review
guix reproducibility
guix reviewed
guix reviewed-looks-good
guix test-tag
guix v1.3.0
However, I do not know how to list all the bugs for the package
guix-patches that matches the usertag reviewed-looks-good. Anyway!
I think that the usertag ’reviewed’ is a good idea. That would be a
very good start. Then if it helps, we could add other usertags as
reviewed-julia for patches that the Julia team can merge.
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. :-)
Well, we can start with one usertag for only the architecture x86_64.
If this one is green, then it is worth to start the review. It would
help for filtering.
The slippery slope is to have too much usertags. I think we should
start with one or two usertags and see if it helps.
WDYT?
Cheers,
simon
next prev parent reply other threads:[~2023-09-07 0:44 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 [this message]
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
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=86sf7qn996.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=guix-devel@gnu.org \
--cc=mail@cbaines.net \
/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).