From: "Ludovic Courtès" <ludo@gnu.org>
To: Greg Hogan <code@greghogan.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: 1.5.0 release?
Date: Fri, 06 Sep 2024 11:32:22 +0200 [thread overview]
Message-ID: <87o751yvo9.fsf@gnu.org> (raw)
In-Reply-To: <CA+3U0Z=L4essa4gbfAOJh5PWnOKrXBKj7yXV0a-hycjfyWoFGw@mail.gmail.com> (Greg Hogan's message of "Wed, 4 Sep 2024 14:51:41 -0400")
Hi Greg,
Greg Hogan <code@greghogan.com> skribis:
> With the recent core-updates merge, and as the master branch
> stabilizes, is there a plan or desire for a 1.5.0 release?
Desire, definitely; plan? we have to come up with one.
I think there should be a team of ~4 volunteers who can commit to focus
on it for, say, 2–5 months¹ (the shorter the better, but we have to
prepare for extra time).
Since I was involved in previous releases, I would be happy to help and
mentor when needed (as an outsider), but I think leadership and
coordination of this effort should come from other community members.
An important skill required here is the ability to keep track of what
needs to be done, what is outside of that scope, coordinating the work
of individuals, and regularly communicating progress with the broader
community. Regular communication is what will allow people to help in
areas they’re familiar with.
I know there are people who’d do a great job on that coordination part
and people who’d be great on the more technical side of things.
Thoughts? Volunteers?
Ludo’.
¹ This has been discussed several times over the past few years. NixOS
has had dedicated release teams for a while: each team is a small
group of people that focuses on one release for a few months, and then
passes on the torch to another group. Rotation is important.
next prev parent reply other threads:[~2024-09-06 9:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-04 18:51 1.5.0 release? Greg Hogan
2024-09-06 9:32 ` Ludovic Courtès [this message]
2024-09-10 22:21 ` Greg Hogan
2024-09-11 14:44 ` Giacomo
2024-09-26 13:09 ` Ludovic Courtès
2024-10-18 21:25 ` Denis 'GNUtoo' Carikli
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=87o751yvo9.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=code@greghogan.com \
--cc=guix-devel@gnu.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.
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).