From: "Ludovic Courtès" <ludo@gnu.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: Attila Lendvai <attila@lendvai.name>,
Suhail Singh <suhailsingh247@gmail.com>,
Simon Tournier <zimon.toutoune@gmail.com>,
guix-devel <guix-devel@gnu.org>
Subject: Re: Automatically testing package updates
Date: Sun, 15 Dec 2024 00:46:26 +0100 [thread overview]
Message-ID: <87wmg1keul.fsf@gnu.org> (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> skribis:
> Attila Lendvai <attila@lendvai.name> 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. As we're
> trying to undo the damage of years of being overwhelmed by patches I'd
> really like to keep the issue tracker for humans only.
I wonder what level of human validation we’d want for “trivial updates”.
In Nixpkgs, IIUC, a bot submits pull requests and a human being
eventually clicks the merge button.
Ludo’.
next prev parent reply other threads:[~2024-12-14 23:47 UTC|newest]
Thread overview: 19+ 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
2024-12-14 23:46 ` Ludovic Courtès [this message]
2024-12-06 4:53 ` Suhail Singh
2024-12-05 19:58 ` Ricardo Wurmus
2024-12-03 0:32 ` Vagrant Cascadian
2024-12-14 23:47 ` Ludovic Courtès
-- strict thread matches above, loose matches on Subject: below --
2024-12-03 14:01 Sharlatan Hellseher
2024-12-14 23:51 ` 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=87wmg1keul.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=attila@lendvai.name \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
--cc=suhailsingh247@gmail.com \
--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 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).