all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Attila Lendvai <attila@lendvai.name>
To: Suhail Singh <suhailsingh247@gmail.com>
Cc: "Ricardo Wurmus" <rekado@elephly.net>,
	"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: Thu, 05 Dec 2024 19:07:22 +0000	[thread overview]
Message-ID: <UyK5AUS0t_4hOooVgcfRLtxe_ItA9r4YDwjKXY4QFZ9YYmj6WUNGTiBVu7Vw5nPba2nfOlTi4YYHW8SqLPjFqCL_Bgnh-2G1cFrhocLbmBo=@lendvai.name> (raw)
In-Reply-To: <87ldwu860j.fsf@gmail.com>

> If we do decide to keep bots in a separate realm as it were, it would be
> desirable (and in my opinion, important) if that still allowed for at
> least as much transparency that the issue tracker provides for human
> activities.


what other data would you miss that is not available in the git log?

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.

for at least two reasons:

 - it's a lot of wasted effort; the admin overhead of a simple package
   update is several times of the effort that goes into creating the
   patch. it gives the impression that the project organization
   doesn't value the time of its participants.

 - when i search for something, it's lost in the noise of boring and
   obsolete stuff in the issue tracker (package updates being one
   source). if a bot joins the "effort", i'm afraid it'll become that
   much worse.

-- 
• attila lendvai
• PGP: 963F 5D5F 45C7 DFCD 0A39
--
“The more artificial taboos and restrictions there are in the world, the more the people are impoverished…. The more that laws and regulations are given prominence, the more thieves and robbers there will be.”
	— Lao Tzu (sixth century BC)



  reply	other threads:[~2024-12-05 19:34 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 [this message]
2024-12-05 19:55             ` Ricardo Wurmus
2024-12-06  5:09               ` Suhail Singh
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='UyK5AUS0t_4hOooVgcfRLtxe_ItA9r4YDwjKXY4QFZ9YYmj6WUNGTiBVu7Vw5nPba2nfOlTi4YYHW8SqLPjFqCL_Bgnh-2G1cFrhocLbmBo=@lendvai.name' \
    --to=attila@lendvai.name \
    --cc=guix-devel@gnu.org \
    --cc=ludo@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 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.