From: ailiop-git <ailiop-git@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: pounce: update to 2.5.
Date: Sat, 25 Sep 2021 14:14:32 +0200 [thread overview]
Message-ID: <20210925121432._A1tx9iJ-oQHMxN-oM_TerypntEeVW3R1R2EFVvID8M@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33110@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1597 bytes --]
New comment by ailiop-git on void-packages repository
https://github.com/void-linux/void-packages/pull/33110#issuecomment-927112757
Comment:
> If we didn't care about testing and some level of QA with updates, we could replace most of your contributions with a cronjob. There's a reason we don't do that.
That's great, but you fail to explain how the checkboxes assist with "testing and some level of QA", or how this adds any confidence on top of travis. This is a very poor signal that bears no significance, and quite honestly it seems like a pointless exercise that is being imposed on contributors.
> If you don't "have the bandwidth" to address test failures or pay attention to PRs after you dump them in the queue, why are you contributing at all?
Because the majority of packages contributed aren't failing, and updates are needed. I'm using those packages and I like contributing so that other users can also receive updates in a timely fashion. I do not submit everything I update (e.g. i've been running on glibc-2.33 since March, but I'm aware of the complications and did not push it upstream).
In the end there are updates that would actually benefit from being done (or at least staged) through a crontab. For example #33102 is urgently needed by users due to multiple apache httpd CVEs. Similarly to other packages, unless I contribute, the package may not be updated for months (apparently their maintainers do not care to check the boxes either).
Still you seem to be more preoccupied and worried about checkboxes rather than how this actually affects users.
next prev parent reply other threads:[~2021-09-25 12:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-25 10:23 [PR PATCH] " ailiop-git
2021-09-25 10:58 ` paper42
2021-09-25 11:00 ` ailiop-git
2021-09-25 11:06 ` paper42
2021-09-25 11:09 ` ailiop-git
2021-09-25 11:25 ` paper42
2021-09-25 11:27 ` Johnnynator
2021-09-25 11:41 ` ailiop-git
2021-09-25 11:58 ` ahesford
2021-09-25 12:03 ` paper42
2021-09-25 12:14 ` ailiop-git [this message]
2021-09-25 13:04 ` ahesford
2021-09-27 11:39 ` [PR PATCH] [Merged]: " paper42
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=20210925121432._A1tx9iJ-oQHMxN-oM_TerypntEeVW3R1R2EFVvID8M@z \
--to=ailiop-git@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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.
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 NNTP newsgroup(s).