From: zimoun <zimon.toutoune@gmail.com>
To: Guix Devel <guix-devel@gnu.org>
Subject: Release v1.4 (or 2.0): process and schedule ?
Date: Fri, 17 Dec 2021 11:03:14 +0100 [thread overview]
Message-ID: <86ilvnh7kt.fsf@gmail.com> (raw)
In-Reply-To: <86ilvq5kmf.fsf@gmail.com>
Hi,
Now core-updates-frozen is merged. Now The Big Change [1 ]is done. Do
we go for v1.4 or v2.0?
In both case, what is the target for a release date? I propose January
31rst. WDYT?
1: <https://guix.gnu.org/en/blog/2021/the-big-change/>
2: <https://lists.gnu.org/archive/html/guix-devel/2021-12/msg00134.html>
On Wed, 15 Dec 2021 at 09:37, zimoun <zimon.toutoune@gmail.com> wrote:
> Now core-udpates is merged, it is good time to make a new release [0].
>
> Schedule? I propose a release date for January, 31st. Early? When?
>
> The branch version-1.4.0 is already created and instead of cherry pick,
> I propose to rebase with master until the freeze. WDYT?
>
> For v1.3, this bug #47297 [1] collected all the blocking items and it
> worked well, I guess. Do we do the same?
>
>
> In any case, to help the release process, please:
>
> a. test – especially the installer [2]
> b. fix bugs severity:important,serious [3,4] or report
> c. proofread the last manual [5]
> d. translate [6]
> e. highlight an item to ease the list of important changes
>
> The lesson of v1.0.1 [#,@] is: please help in testing the installer. :-)
>
>
> How does it sound?
>
> Last, Guix is a “rolling-release“, so what does it mean ‘release’? :-)
> The main argument for releasing, IMHO, is communication and so attract
> potential new users. :-)
>
> Cheers,
> simon
>
> [0]: <https://yhetil.org/guix/8735mwc6l1.fsf@gmail.com>
> [1] <https://issues.guix.gnu.org/47297>
> [2] <https://guix.gnu.org/manual/devel/en/guix.html#System-Installation>
> [3] <http://issues.guix.gnu.org/search?query=severity%3Aserious+is%3Aopen>
> [4] <http://issues.guix.gnu.org/search?query=severity%3Aimportant+is%3Aopen>
> [5] <https://guix.gnu.org/manual/devel/en/guix.html>
> [6] <https://guix.gnu.org/manual/devel/en/html_node/Translating-Guix.html>
>
> [#] <https://guix.gnu.org/en/blog/2019/gnu-guix-1.0.1-released/>
> [@] <https://issues.guix.gnu.org/issue/35541>
Cheers,
simon
next prev parent reply other threads:[~2021-12-17 10:07 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 ` zimoun [this message]
2021-12-20 2:12 ` Release v1.4 (or 2.0): " 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
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
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=86ilvnh7kt.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--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).