all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Suhail Singh <suhailsingh247@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: "Attila Lendvai" <attila@lendvai.name>,
	"Suhail Singh" <suhailsingh247@gmail.com>,
	"Simon Tournier" <zimon.toutoune@gmail.com>,
	"Ludovic Courtès" <ludo@gnu.org>, guix-devel <guix-devel@gnu.org>
Subject: Re: Automatically testing package updates
Date: Fri, 06 Dec 2024 00:09:01 -0500	[thread overview]
Message-ID: <87zfl9e6tu.fsf@gmail.com> (raw)
In-Reply-To: <87r06l7vlm.fsf@elephly.net> (Ricardo Wurmus's message of "Thu, 05 Dec 2024 20:55:49 +0100")

Ricardo Wurmus <rekado@elephly.net> writes:

>> sidenote: as a newcomer i found it rather off-putting that the bug
>> tracker is full of random two-liner package updates, many long
>> forgotten and even obsolete.
>
> This is exactly my point and why I think the bug tracker must contain
> only *actionable* work that humans are meant to work on.

I believe it's only required that the bug tracker provide a way to limit
results to only humanly-generated-patches.

If by bug tracker we mean the mumi instance at issues.gnu.guix.org note
that something like the above already happens today.  The debbugs
instance is shared with Emacs.  However, bugs relating to the "emacs"
user don't show up in the search results in the mumi interface.  All
currently humanly-generated patches sent to guix-patches are assigned
the user "guix".  It would be possible to have the bot-generated patches
be assigned a different user, or if the same user, a specific user-tag
that is filtered out by mumi in the search results.

There may be possibly other reasons why we don't want to do so.
However, being able to only focus on the humanly-generated-patches isn't
such a reason.

-- 
Suhail


  reply	other threads:[~2024-12-06  5:10 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-02 13:44 Automatically testing package updates Ludovic Courtès
2024-12-02 14:50 ` Simon Tournier
2024-12-02 19:14 ` Simon Tournier
2024-12-02 19:16   ` Simon Tournier
2024-12-05  7:20   ` Efraim Flashner
2024-12-05  8:06     ` Hilton Chain
2024-12-05  9:23       ` Ricardo Wurmus
2024-12-05 13:29     ` Suhail Singh
2024-12-05 15:31       ` Ricardo Wurmus
2024-12-05 16:10         ` Suhail Singh
2024-12-05 19:07           ` Attila Lendvai
2024-12-05 19:55             ` Ricardo Wurmus
2024-12-06  5:09               ` Suhail Singh [this message]
2024-12-06  4:53             ` Suhail Singh
2024-12-05 19:58           ` Ricardo Wurmus
2024-12-03  0:32 ` Vagrant Cascadian

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87zfl9e6tu.fsf@gmail.com \
    --to=suhailsingh247@gmail.com \
    --cc=attila@lendvai.name \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.org \
    --cc=rekado@elephly.net \
    --cc=zimon.toutoune@gmail.com \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.