unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Julien Lepiller <julien@lepiller.eu>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>,
	guix-devel@gnu.org
Cc: "Ludovic Courtès" <ludo@gnu.org>
Subject: Re: GNU Guix 1.4.0rc1 available for testing!
Date: Sun, 04 Dec 2022 19:30:58 +0100	[thread overview]
Message-ID: <C74DC399-4F96-4791-A2F3-702850C786D8@lepiller.eu> (raw)
In-Reply-To: <87fsdvw3bx.fsf@pelzflorian.de>

[-- Attachment #1: Type: text/plain, Size: 1254 bytes --]

For i18n, weblate is still following master. I'll switch when we start string freeze, which should be one week before release. When the time comes, please someone ping me :)

Le 4 décembre 2022 17:17:38 GMT+01:00, "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> a écrit :
>There are some release blockers.  To summarize, IMHO it would be
>regrettable if these bugs were not fixed before release:
>
>* [PATCH v2 2/3] install: Add missing e2fsprogs utility.
>  <https://issues.guix.gnu.org/59661>
>  Otherwise manual installation does not work as advertised.
>
>* [version 1.4.0rc1] reconfigure fails
>  <https://issues.guix.gnu.org/59780>
>  Otherwise users cannot update Guix System once installed
>  unless they take manual action.
>
>* [version 1.4.0rc1] install.sh script should authorize bordeaux
>  <https://issues.guix.gnu.org/59781>
>  Otherwise especially ARM users get far less substitutes
>  unless they take manual action.
>
>Julien Lepiller <julien@lepiller.eu> writes:
>> Do we string freeze?
>
>About string freeze: I do not know if that is the case, but changes to
>critical parts of doc/guix.texi on master should not be reflected on
>Weblate if they don’t get into 1.4.0.
>
>Regards,
>Florian

[-- Attachment #2: Type: text/html, Size: 1836 bytes --]

  reply	other threads:[~2022-12-04 18:31 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-01  9:17 GNU Guix 1.4.0rc1 available for testing! Ludovic Courtès
2022-12-01 15:38 ` Luis Felipe
2022-12-01 21:40 ` Luis Felipe
2022-12-02  9:06   ` Ludovic Courtès
2022-12-01 22:55 ` Svante Signell
2022-12-03 22:46   ` pelzflorian (Florian Pelz)
2022-12-02 22:17 ` Ahmed Khanzada
2022-12-02 23:10   ` (
2022-12-03  9:50   ` zimoun
2022-12-03 14:18     ` Ahmed Khanzada
2022-12-03 17:45       ` Ludovic Courtès
2022-12-03 16:25     ` Kaelyn
2022-12-04 15:50       ` Ahmed Khanzada via Development of GNU Guix and the GNU System distribution.
2022-12-04  1:19 ` John Kehayias
2022-12-04 16:17 ` pelzflorian (Florian Pelz)
2022-12-04 18:30   ` Julien Lepiller [this message]
2022-12-06 10:46   ` 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=C74DC399-4F96-4791-A2F3-702850C786D8@lepiller.eu \
    --to=julien@lepiller.eu \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.org \
    --cc=pelzflorian@pelzflorian.de \
    /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).