all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Julien Lepiller <julien@lepiller.eu>
To: guix-devel@gnu.org, "Vagrant Cascadian" <vagrant@debian.org>,
	"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: Sun, 16 May 2021 12:47:42 -0400	[thread overview]
Message-ID: <50C99522-9DD4-4889-891A-98E83E87AEB3@lepiller.eu> (raw)
In-Reply-To: <87tun2wtsx.fsf@yucca>

[-- Attachment #1: Type: text/plain, Size: 1532 bytes --]

I agree string freeze was way too long for this release. We entered string freeze one week before the planned release date, it got pushed by almost one month.

For next release, I think it would be better to enter string freeze along with rc1 or a bit later, but always at least give one week before release (so a late string freeze could delay release by a few days).

Le 16 mai 2021 12:02:38 GMT-04:00, Vagrant Cascadian <vagrant@debian.org> a écrit :
>On 2021-05-16, Maxim Cournoyer wrote:
>> 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.
>
>It would be nice to get a Release Candidate (or Pre Release?) out with
>some time before the string freeze; it's easiest for me to do the
>spelling/grammar/typo checks and fixes after the first RC tarball (as
>it
>is basically just part of my packaging for Debian workflow), but was a
>little disappointing to not be able to get such trivial fixes into the
>release.
>
>Alternately or additionally, setting up a "make dist" job on
>ci.guix.gnu.org and publishing the resulting tarball somewhere would
>allow me to check at arbitrary points during the release cycle and
>catch
>things earlier.
>
>
>live well, 
>  vagrant

[-- Attachment #2: Type: text/html, Size: 1916 bytes --]

  reply	other threads:[~2021-05-18 15:42 UTC|newest]

Thread overview: 26+ 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  7:58 ` Paul Jewell
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 [this message]
2021-05-17 12:55     ` zimoun
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=50C99522-9DD4-4889-891A-98E83E87AEB3@lepiller.eu \
    --to=julien@lepiller.eu \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.org \
    --cc=maxim.cournoyer@gmail.com \
    --cc=vagrant@debian.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 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.