From: LaszloGombos <LaszloGombos@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: dracut: update to 059.20231027
Date: Sat, 28 Oct 2023 16:38:11 +0200 [thread overview]
Message-ID: <20231028143811.2trXwwFPx8W0pIViNoVlvqq9t2Lh0CymUIjrloZqoHk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46936@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1216 bytes --]
New comment by LaszloGombos on void-packages repository
https://github.com/void-linux/void-packages/pull/46936#issuecomment-1783832638
Comment:
> I'm not seeing anything in the linked issue that indicates why releases are stalled. Is there an issue I can follow that tracks that problem?
This is indeed the key issue here. I think @ahesford 's comment is already a great summary of the situation, but just to add...
> Currently only Github project admins can tag git commits in this project. The current project admins are documented in the wiki - https://github.com/dracutdevs/dracut/wiki/Dracut-development
At closer look you would notice that none of the project admins are active, and the remaining active maintainers are not able to make a tagged release. Here is one more pointer of a failed release attempt from July: https://github.com/dracutdevs/dracut/issues/2444
> If this problem continues indefinitely, we can investigate other alternatives for keeping Dracut up to date.
I just wanted to get a sense of how much this community is willing to wait for a release for something as critical to the boot process of the system. I think it is reasonable to revisit this issue in e.g. in 2024.
next prev parent reply other threads:[~2023-10-28 14:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-28 3:36 [PR PATCH] dracut: update to 059+git20231027 LaszloGombos
2023-10-28 3:38 ` classabbyamp
2023-10-28 3:38 ` classabbyamp
2023-10-28 3:45 ` [PR PATCH] [Updated] " LaszloGombos
2023-10-28 3:45 ` LaszloGombos
2023-10-28 3:49 ` [PR PATCH] [Updated] dracut: update to 059.20231027 LaszloGombos
2023-10-28 3:55 ` LaszloGombos
2023-10-28 3:58 ` LaszloGombos
2023-10-28 3:59 ` [PR PATCH] [Updated] " LaszloGombos
2023-10-28 11:33 ` ahesford
2023-10-28 11:33 ` [PR PATCH] [Closed]: " ahesford
2023-10-28 12:08 ` LaszloGombos
2023-10-28 12:09 ` LaszloGombos
2023-10-28 13:43 ` ahesford
2023-10-28 13:44 ` ahesford
2023-10-28 13:44 ` ahesford
2023-10-28 13:51 ` zdykstra
2023-10-28 14:38 ` LaszloGombos [this message]
2023-10-28 14:51 ` zdykstra
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=20231028143811.2trXwwFPx8W0pIViNoVlvqq9t2Lh0CymUIjrloZqoHk@z \
--to=laszlogombos@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).