From: "Ludovic Courtès" <ludo@gnu.org>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: Vagrant Cascadian <vagrant@debian.org>, Guix Devel <guix-devel@gnu.org>
Subject: Re: Release v1.4 (or 2.0): process and schedule ?
Date: Mon, 03 Jan 2022 15:33:19 +0100 [thread overview]
Message-ID: <87y23wkhxs.fsf@gnu.org> (raw)
In-Reply-To: <87y246wvza.fsf@gmail.com> (Maxim Cournoyer's message of "Sun, 26 Dec 2021 22:46:33 -0500")
Hello!
Maxim Cournoyer <maxim.cournoyer@gmail.com> skribis:
> About the current status, I'm nearing on pushing a version-1.4.0 branch
> which is based on master with a few more (core-ish) updates. There's
> still a few days ahead of that, so if you manage to get many of this
> kind of problems fixed & merged in master they can easily be included in
> the next release.
Before the first RC, I’d like to push the latest ‘guix style’ changes:
<https://issues.guix.gnu.org/52974>.
Do we enter string freeze before the first RC? I forgot how we did it
last time.
Thanks,
Ludo’.
next prev parent reply other threads:[~2022-01-03 14:33 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-15 8:37 Release process and schedule ? zimoun
2021-12-17 10:03 ` Release v1.4 (or 2.0): " zimoun
2021-12-20 2:12 ` Maxim Cournoyer
2021-12-20 3:43 ` raingloom
2021-12-20 9:04 ` zimoun
2021-12-20 9:14 ` zimoun
2021-12-20 21:24 ` Ludovic Courtès
2021-12-20 22:54 ` zimoun
2021-12-20 18:12 ` Bengt Richter
2021-12-21 20:48 ` Vagrant Cascadian
2021-12-21 21:20 ` Vagrant Cascadian
2022-01-03 14:31 ` Ludovic Courtès
2022-01-03 16:32 ` Vagrant Cascadian
2021-12-27 3:46 ` Maxim Cournoyer
2022-01-03 14:33 ` Ludovic Courtès [this message]
2022-01-04 16:24 ` Maxim Cournoyer
2022-01-04 19:32 ` Chris Marusich
2022-01-06 13:49 ` Maxim Cournoyer
2022-01-09 2:21 ` Chris Marusich
2022-01-18 5:05 ` Maxim Cournoyer
2022-01-18 13:20 ` Ludovic Courtès
2022-01-15 19:26 ` Vagrant Cascadian
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=87y23wkhxs.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@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.