From: "Ludovic Courtès" <ludo@gnu.org>
To: zimoun <zimon.toutoune@gmail.com>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Release 1.2.1: timeline
Date: Mon, 15 Mar 2021 17:55:21 +0100 [thread overview]
Message-ID: <87h7lce4qu.fsf@gnu.org> (raw)
In-Reply-To: <867dmcifii.fsf@gmail.com> (zimoun's message of "Fri, 12 Mar 2021 16:00:05 +0100")
Hello!
zimoun <zimon.toutoune@gmail.com> skribis:
> The plan is to release on the April, 18th. It is a target date.
I want to believe! :-)
> We are planning an «ungraftathon» the last week-end of March (27-28).
> Please roam on #guix if you want to help.
+1
> A draft of the timeline is:
>
> - until April 1rst: fixes, check substitute availability, etc.
> - as soon as possible: start to build wip-next-release
> - merge branch wip-next-release when ready
> - on Monday 12th April, string freeze
> - couple of days after, branch the release and write the materials
> (ChangeLog and posts)
> - release
Sounds reasonable to me.
> The architecture armf will not be included.
Wait wait, I missed that. What happened? I think we should include it,
even if substitute availability remains low.
> The branch core-updates will not be merged.
Yeah, that sounds like the most reasonable approach.
> Once this release is done, we could write a timeline for the next
> core-updates merge and list what should be included in the next
> release (1.2.2 or 1.3). Somehow, all this is an “experiment” for a
> webpage detailing the different timelines.
>
> Does it make sense?
It does. Thanks for helping us stay on track!
Ludo’.
next prev parent reply other threads:[~2021-03-15 16:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-12 15:00 Release 1.2.1: timeline zimoun
2021-03-15 16:55 ` Ludovic Courtès [this message]
2021-03-15 17:08 ` Vincent Legoll
2021-03-15 18:14 ` Leo Famulari
2021-03-15 20:15 ` Vincent Legoll
2021-03-15 20:27 ` Leo Famulari
2021-03-17 17:28 ` armhf-linux substitutes Ludovic Courtès
2021-03-17 18:56 ` zimoun
2021-03-29 7:21 ` Mathieu Othacehe
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=87h7lce4qu.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--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).