From: zimoun <zimon.toutoune@gmail.com>
To: Chris Marusich <cmmarusich@gmail.com>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Release 1.2.1: status
Date: Fri, 19 Mar 2021 09:50:55 +0100 [thread overview]
Message-ID: <86h7l7r0gg.fsf@gmail.com> (raw)
In-Reply-To: <875z1n1wfb.fsf@gmail.com>
Hi Chris,
On Thu, 18 Mar 2021 at 23:37, Chris Marusich <cmmarusich@gmail.com> wrote:
> More review is welcome, but unless some unforeseen issues are
> discovered, I agree that we can go ahead with adding support for
> powerpc64le-linux.
Great!
> Where is the release work happening? Where can I merge or apply these
> changes to ensure they get included in the next release?
The release work happens on master. The branch wip-next-release
contains fixes, but AFAIK, it is not built by the CI, and these fixes
are ’core-updates’-like changes; I do not know if it is doable to merge
on time.
Well, maybe the patches could be directly applied to master, IMHO.
Quote the proposed Release timeline [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
Cheers,
simon
PS: Sorry if the release process appears unclear. Based on the
experiences of 1.2.0 and now this one, the idea is to propose then a
clear documented timeline for the next releases. Basically, some
technical items are described in maintenance/doc/release.org [2] and
from my point of view, some items describing the (timeline) process
should be added. Maybe in the manual so that we all know what we can
«expect».
1: <https://yhetil.org/guix/867dmcifii.fsf@gmail.com>
2: <https://git.savannah.gnu.org/cgit/guix/maintenance.git/tree/doc/release.org>
next prev parent reply other threads:[~2021-03-19 8:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-18 14:28 Release 1.2.1: status zimoun
2021-03-19 6:37 ` Chris Marusich
2021-03-19 8:27 ` Christopher Baines
2021-03-19 8:50 ` zimoun [this message]
2021-03-20 18:09 ` Leo Famulari
2021-03-20 22:56 ` zimoun
2021-03-20 23:21 ` Leo Famulari
2021-03-19 18:31 ` Andreas Enge
2021-03-19 21:59 ` Luis Felipe
2021-03-20 23:03 ` zimoun
2021-03-19 22:26 ` Luis Felipe
2021-03-21 0:16 ` zimoun
2021-03-21 14:13 ` Luis Felipe
2021-03-20 20:01 ` Leo Famulari
2021-03-20 23:00 ` zimoun
2021-03-21 17:54 ` Leo Famulari
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=86h7l7r0gg.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=cmmarusich@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).