unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: "Maxim Cournoyer" <maxim.cournoyer@gmail.com>,
	"Ludovic Courtès" <ludo@gnu.org>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: GNU Guix 1.4.0 in September? (was: Re: GNU Guix 1.3.0 released)
Date: Mon, 17 May 2021 14:55:39 +0200	[thread overview]
Message-ID: <86lf8dr038.fsf@gmail.com> (raw)
In-Reply-To: <87tun2om0a.fsf_-_@gmail.com>

Hi Maxim,

>> Note also that we were “only” 3 weeks late thanks to the hard work of
>> zimoun and Leo early on keeping track of everything that needed to be
>> addressed.  If someone wants to propose a date for the next release and
>> take responsibility as “release keeper”, we’ll all welcome that!
>
> Yes, thank you Simon and Leo for the help with the release!  I felt less
> lonely :-).  I've learned that producing a release can easily take 2-3
> weeks even in good conditions (e.g., not many blockers to fix).  I'd
> suggest anyone (myself included :-)) trying to meet the schedule to
> seriously start trying to put out RCs a month before the planned release
> date.

Thank you!  And thanks to all the people involved. :-)

For what it is worth, the anniversary dates seems good targets as
release dates:

 - April, 18th (init commit) 
 - November, 23rd (first announce)

Do you plan to keep a Release Bug open with all the blocking bugs?  Does
it help?  If yes, does it make sense to start now to add some or only ~2
months before the target?

> Perhaps we can aim for the next release mid-September (core-updates).
> I'm not too sure of the status of core-updates right now, but last time
> I worked on it was in a rather good state.

I remember a plot sent to guix-maintaainers about the number of grafts,
the core-updates merges and the release dates.  I am not sure it is
really interesting and it is worth to resend it, or maybe dumping the
Cuirass database to investigate a bit more.  Well, my point is the
core-updates merges and the release dates should be synchronized; say
target the core-updates for end of September, then the release for
November.  To me, this synchronisation makes senses because it
constraints the ~6months core-updates cycle and in the same time, the 2
releases per year.


Cheers,
simon


  parent reply	other threads:[~2021-05-17 13:08 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-12  6:40 GNU Guix 1.3.0 released Maxim Cournoyer
2021-05-12 11:43 ` 宋文武
2021-05-12 12:35   ` Mathieu Othacehe
     [not found] ` <Maxim Cournoyer's message of "Wed, 12 May 2021 02:40:39 -0400">
     [not found]   ` <OSZP286MB06642FFB3BB362E2E85BE9D4A3529@OSZP286MB0664.JPNP286.PROD.OUTLOOK.CO M>
2021-05-12 12:02     ` maxxcan--- via
2021-05-15 16:42 ` Ludovic Courtès
2021-05-16 13:18   ` GNU Guix 1.4.0 in September? (was: Re: GNU Guix 1.3.0 released) Maxim Cournoyer
2021-05-16 16:02     ` Vagrant Cascadian
2021-05-16 16:47       ` Julien Lepiller
2021-05-17 12:55     ` zimoun [this message]
2021-05-17 14:43       ` Leo Famulari
2021-05-17 15:01         ` GNU Guix 1.4.0 in September? Maxim Cournoyer
2021-05-17 17:35         ` GNU Guix 1.4.0 in September? (was: Re: GNU Guix 1.3.0 released) Bengt Richter
2021-05-17 20:29           ` GNU Guix 1.4.0 in September? Maxim Cournoyer
2021-05-17 20:34       ` Maxim Cournoyer
2021-05-17 20:32     ` Ludovic Courtès
2021-06-16  7:49     ` Chris Marusich
2021-06-20 16:26       ` Debbugs user tags Ludovic Courtès
2021-06-23  2:48         ` Chris Marusich
2021-06-23 13:53           ` Ludovic Courtès
2021-06-24  4:59             ` Chris Marusich
2021-06-24 19:48       ` GNU Guix 1.4.0 in September? Maxim Cournoyer
2021-06-24 20:48         ` Debbugs Usertags - which user to use? (Was: Re: GNU Guix 1.4.0 in September?) Chris Marusich
2021-06-25  3:23           ` Debbugs Usertags - which user to use? Maxim Cournoyer
2021-07-06  4:22             ` Chris Marusich
2021-07-06 16:10               ` 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=86lf8dr038.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.org \
    --cc=maxim.cournoyer@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).