From: Tobias Platen <guix@platen-software.de>
To: guix-devel@gnu.org
Subject: Re: GNU Guix 1.4.0 released
Date: Sat, 14 Jan 2023 13:04:10 +0100 [thread overview]
Message-ID: <9c49c14274111b0cdae548867a6ce946b8f44b9e.camel@platen-software.de> (raw)
In-Reply-To: <86wn618ft5.fsf@gmail.com>
Hi,
Currently I am testing that one on my ThinkPad X200 and on my Talos II.
Tobias Alexandra
On Thu, 2023-01-05 at 10:57 +0100, Simon Tournier wrote:
> Hi Ludo, all,
>
> On Tue, 03 Jan 2023 at 10:08, Ludovic Courtès <ludo@gnu.org> wrote:
>
> > In my experience though, a lot of the work is coordination: keeping
> > track of what needs to be done, open bugs, calling for testing,
> > etc.
>
> Yes, coordination is large part of the work, but not only as shown by
> previous experiences (e.g., [1,2,3,4] and older others).
>
> 1: <https://yhetil.org/guix/86bkvckcgr.fsf@gmail.com>
> 2: <https://yhetil.org/guix/86ilvq5kmf.fsf@gmail.com>
> 3: <https://yhetil.org/guix/87tun2om0a.fsf_-_@gmail.com>
> 4: <https://yhetil.org/guix/867dmcifii.fsf@gmail.com>
>
>
> > 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. :-)
>
> 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>
>
>
> Cheers,
> simon
>
prev parent reply other threads:[~2023-01-14 12:04 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 ` Setting up the release team Ludovic Courtès
2023-01-14 12:04 ` Tobias Platen [this message]
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=9c49c14274111b0cdae548867a6ce946b8f44b9e.camel@platen-software.de \
--to=guix@platen-software.de \
--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).