From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: zimoun <zimon.toutoune@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: core-updates-frozen branch merged
Date: Tue, 14 Dec 2021 14:25:16 -0500 [thread overview]
Message-ID: <87ee6f9eg3.fsf@gmail.com> (raw)
In-Reply-To: <CAJ3okZ2aeePQt-DD=LisbkSTF9Kn2DU3c9ZSnNj6Rs6AF-CYMA@mail.gmail.com> (zimoun's message of "Tue, 14 Dec 2021 15:20:45 +0100")
Hi!
zimoun <zimon.toutoune@gmail.com> writes:
> Hi Josselin,
>
> On Tue, 14 Dec 2021 at 14:24, Josselin Poiret <dev@jpoiret.xyz> wrote:
>
>> What exactly would those "release-specific enhancements" be?
>
> Basically,
>
> - Fix important bugs and/or blocking ones (I do not know if there are
> many today). And previous release, a "release" bug had been opened to
> collect them.
> - Make sure that all work as expected: test installers etc.
> - String freeze for documentation updates. Let the time for translators.
> - Update changelog / NEWS
> - Write blog post
Yes, this, and I was also thinking the occasional change that'd cause
too many rebuilds for master, such as fixing up sitecustomize.py [0]
that basically triggers a world rebuild if we want to ship it in the
next release. We could batch others as well; I know that bumping our
xorg package to the recently released 1.7.3 would be nice to fix the
spurious warnings. [1]
[0] https://issues.guix.gnu.org/52269
[1] https://lists.x.org/archives/xorg-announce/2021-December/003120.html
Thanks all for the great collaboration that went into readying
core-updates-frozen for the merge! :-)
Maxim
next prev parent reply other threads:[~2021-12-14 19:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-14 1:34 core-updates-frozen branch merged Maxim Cournoyer
2021-12-14 4:30 ` Timothy Sample
2021-12-14 6:26 ` zimoun
2021-12-14 7:31 ` Mathieu Othacehe
2021-12-14 13:16 ` Josselin Poiret
2021-12-14 14:20 ` zimoun
2021-12-14 19:25 ` Maxim Cournoyer [this message]
2021-12-14 15:42 ` Katherine Cox-Buday
2021-12-15 21:22 ` Thiago Jung Bauermann
2021-12-20 17:55 ` Ludovic Courtès
2021-12-22 3:48 ` 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=87ee6f9eg3.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--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 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.