From: "Ludovic Courtès" <ludo@gnu.org>
To: Simon Tournier <zimon.toutoune@gmail.com>
Cc: Maxim Cournoyer <maxim.cournoyer@gmail.com>, guix-devel@gnu.org
Subject: Setting up the release team
Date: Mon, 09 Jan 2023 18:19:24 +0100 [thread overview]
Message-ID: <87358jr5gj.fsf_-_@gnu.org> (raw)
In-Reply-To: <86wn618ft5.fsf@gmail.com> (Simon Tournier's message of "Thu, 05 Jan 2023 10:57:10 +0100")
Hello!
Simon Tournier <zimon.toutoune@gmail.com> skribis:
>> I think we should start thinking about the next release, forming a
>> small release team, and I’ll be happy to mentor!
>
> Definitively! Count on me to candidate on such team. :-)
Yay, thank you!!
Who else is able and willing to dedicate time to this? I think work
could actually start real soon.
As I see it, people on the release team will *not* do all the work.
Rather, they will keep track of things and make sure we together tackle
the relevant tasks so we converge towards a release. It does not have
to be very technical.
> From my point of view, this team will be a rotating effort. For
> instance, from 2 to 4 people will be part. The duty is to be part for 2
> releases; 1-2 person step downs for welcoming 1-2 new person after each
> release. Well, something similar to NixOS release management.
>
> As usual, the question is about the bootstrap. ;-)
>
> 5: <https://nixos.org/community/teams/nixos-release.html>
> 6: <https://nixos.github.io/release-wiki/Release-Management-Team.html>
Agreed, that would be ideal.
I think we should formalize it at some point along the lines of what
NixOS did, presumably with a section in the manual.
Thanks,
Ludo’.
next prev parent reply other threads:[~2023-01-09 17:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-19 14:25 GNU Guix 1.4.0 released Ludovic Courtès
2022-12-27 3:37 ` Maxim Cournoyer
2023-01-03 9:08 ` Ludovic Courtès
2023-01-03 15:08 ` Maxim Cournoyer
2023-01-03 16:09 ` indieterminacy
2023-01-03 18:42 ` Joshua Branson
2023-01-03 20:35 ` indieterminacy
2023-01-03 23:16 ` indieterminacy
2023-01-05 9:57 ` Simon Tournier
2023-01-09 17:19 ` Ludovic Courtès [this message]
2023-01-14 12:04 ` Tobias Platen
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=87358jr5gj.fsf_-_@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=maxim.cournoyer@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.