unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andreas Enge <andreas@enge.fr>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Christopher Baines <mail@cbaines.net>,
	Simon Tournier <zimon.toutoune@gmail.com>,
	Guix Devel <guix-devel@gnu.org>
Subject: Re: Scheduling a new release?
Date: Wed, 15 May 2024 12:37:08 +0200	[thread overview]
Message-ID: <ZkSQVFXmF5mJ23sv@jurong> (raw)
In-Reply-To: <87seyk4to9.fsf@gnu.org>

Am Tue, May 14, 2024 at 11:41:26AM +0200 schrieb Ludovic Courtès:
> As discussed at the 2023 Guix Days (!), we could follow a model similar
> to that of NixOS: form a release team (~4 people) dedicated to keeping
> track of issues in particular wrt. the installer, and committed to
> publishing a release within 4–6 months. (I think several people actually
> volunteered back in Feb. 2023. :-))

That is a good approach, of course.

The two things I think should happen before a release is merging
core-updates, and making a rebuild round (or several rounds? I am unsure
whether it is safe to do everything at once) ungrafting everything.
Plus testing the installer etc.

Andreas



  reply	other threads:[~2024-05-15 10:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-06 11:12 Scheduling a new release? Simon Tournier
2024-05-06 11:17 ` Simon Tournier
2024-05-08 13:01 ` Christopher Baines
2024-05-14  9:41   ` Ludovic Courtès
2024-05-15 10:37     ` Andreas Enge [this message]
2024-05-14 10:19   ` Christina O'Donnell
2024-05-14 13:45     ` Christopher Baines
2024-05-21 23:42     ` bug#70662: Problems building nss@3.98.0 Maxim Cournoyer

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=ZkSQVFXmF5mJ23sv@jurong \
    --to=andreas@enge.fr \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.org \
    --cc=mail@cbaines.net \
    --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 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).