From: Julien Lepiller <julien@lepiller.eu>
To: guix-devel@gnu.org, zimoun <zimon.toutoune@gmail.com>,
"Ludovic Courtès" <ludo@gnu.org>,
"Mathieu Othacehe" <othacehe@gnu.org>
Subject: Re: ‘version-1.2.0’ branch created!
Date: Fri, 06 Nov 2020 08:16:49 -0500 [thread overview]
Message-ID: <5323273B-1B70-40BE-A58E-12456F386F99@lepiller.eu> (raw)
In-Reply-To: <867dqyfy25.fsf@gmail.com>
Le 6 novembre 2020 07:51:30 GMT-05:00, zimoun <zimon.toutoune@gmail.com> a écrit :
>Hi,
>
>On Fri, 06 Nov 2020 at 11:15, Ludovic Courtès <ludo@gnu.org> wrote:
>
>> We have a new branch now!
>
>Awesome!
>
>
>> This branch should take primarily important changes that fix the
>> installer or other key elements. It should not change translatable
>> strings and should not change the manual either, unless a fix
>requires
>> it, because translations are being finalized.
>
>We are in string freeze. Translators, is it fine for you?
We'll need some time to adjust the translation for the release. I've sent the new strings to the TP coordinator yesterday, but they're not on the TP yet.
>
>
>> It may be OK to merge “obvious” changes from ‘master’, such as the
>> addition or upgrade of leaf packages. Changes that would lead to
>> rebuilds of key packages (everything the installer needs plus GNOME,
>> Emacs, IceCat, etc.) should be avoided I think.
>
>Agree.
>
>
>> Thoughts? Patches? Ideas? :-)
>
>A lot of substitutes are still missing (for example R). Is it possible
>to trigger the builds?
>
>
>All the best,
>simon
next prev parent reply other threads:[~2020-11-06 13:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-06 10:15 ‘version-1.2.0’ branch created! Ludovic Courtès
2020-11-06 12:51 ` zimoun
2020-11-06 13:16 ` Julien Lepiller [this message]
2020-11-10 13:32 ` zimoun
2020-11-08 2:10 ` Oleg Pykhalov
2020-11-08 17:38 ` Ludovic Courtès
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=5323273B-1B70-40BE-A58E-12456F386F99@lepiller.eu \
--to=julien@lepiller.eu \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=othacehe@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).