unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Christopher Baines <mail@cbaines.net>
To: jgart <jgart@dismail.de>
Cc: guix-devel@gnu.org
Subject: Re: Automated Patch Review Wish List
Date: Wed, 16 Nov 2022 16:02:18 +0000	[thread overview]
Message-ID: <87cz9mg9zi.fsf@cbaines.net> (raw)
In-Reply-To: <20221116063201.GC3370@dismail.de>

[-- Attachment #1: Type: text/plain, Size: 965 bytes --]


jgart <jgart@dismail.de> writes:

> On Wed, 16 Nov 2022 08:45:34 +0000 Christopher Baines <mail@cbaines.net> wrote:
>> I'm not sure what you're asking. Are you asking what people think is
>> most important to automate about patch review?
>
> Yup, what's the top priority feature we want to implement first/next for
> having a more automated patch review process?

At least in terms of what's going on at qa.guix.gnu.org, I've nearly
finished adding better support to the Guix Data Service to identify
where builds are blocked by other failures.

There's still some more testing to do, but that information is now taken
in to account. I'm hoping this will make the comparisons clearer.

In terms of what to implement next, there's a TODO list here [1], but
personally I'm going to try and get back to using and trying to
encourage others to use qa.guix.gnu.org when reviewing patches.

1: https://git.cbaines.net/guix/qa-frontpage/about/#org18a0c6a

Thanks,

Chris

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]

  reply	other threads:[~2022-11-16 16:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-16  4:08 Automated Patch Review Wish List jgart
2022-11-16  8:45 ` Christopher Baines
2022-11-16 12:32   ` jgart
2022-11-16 16:02     ` Christopher Baines [this message]
2022-11-16 16:47       ` jgart
2022-11-16 17:24         ` Christopher Baines
2022-11-16 18:25         ` Luis Felipe
2022-11-16 18:32           ` Christopher Baines

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=87cz9mg9zi.fsf@cbaines.net \
    --to=mail@cbaines.net \
    --cc=guix-devel@gnu.org \
    --cc=jgart@dismail.de \
    /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).