unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Julien Lepiller <julien@lepiller.eu>
Cc: Guix-devel <guix-devel@gnu.org>,
	 guix-maintainers@gnu.org,  Marius Bakke <marius@gnu.org>
Subject: Re: Planning for a release, for real
Date: Fri, 07 Oct 2022 11:49:21 +0200	[thread overview]
Message-ID: <87edvkc6am.fsf@gnu.org> (raw)
In-Reply-To: <FBF34AED-7CA3-427F-A675-6E6634DD22B2@lepiller.eu> (Julien Lepiller's message of "Thu, 06 Oct 2022 18:02:47 +0200")

Hi,

Julien Lepiller <julien@lepiller.eu> skribis:

> I'll take care of the cranslations (notifying translators, ensuring string freeze is respected, …)

Great, thanks.

> We need to be careful not to start the stsing freeze step too early. Last time (or previous?) we started a week before the scheduled release date, but the schedule slipped by a few weeks and we had some pressure in the pipeline because some patches could not be applied because of string changes.
>
> Let's try to have a better vision on the planning this time :)

Right!  How long do you think we need for the string freeze?

I feel that thanks to Weblate translations are continuously updated, so
maybe things can be frozen for a shorter period of time?

Thanks,
Ludo’.


  reply	other threads:[~2022-10-07  9:49 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-06 14:50 Planning for a release, for real Ludovic Courtès
2022-10-06 16:02 ` Julien Lepiller
2022-10-07  9:49   ` Ludovic Courtès [this message]
2022-10-07 10:14     ` Julien Lepiller
2022-10-06 16:07 ` Maxime Devos
2022-10-07  9:50   ` Ludovic Courtès
2022-10-07  9:53     ` Maxime Devos
2022-10-07  6:20 ` Supported architectures Efraim Flashner
2022-10-07 10:02   ` Ludovic Courtès
2022-10-10  7:57   ` Csepp
2022-10-12 20:40   ` Vagrant Cascadian
2022-10-13 15:06     ` Ludovic Courtès
2022-10-07  8:26 ` Planning for a release, for real Christopher Baines
2022-10-07 10:09   ` Ludovic Courtès
2022-10-10 10:33 ` zimoun
2022-10-13 15:19 ` Release progress, week 1 Ludovic Courtès
2022-10-13 15:33   ` Efraim Flashner
2022-10-13 15:42   ` Christopher Baines
2022-10-20 13:49   ` Release progress, week 2 Ludovic Courtès
2022-10-20 20:07     ` Efraim Flashner
2022-10-21  8:51       ` Rust on aarch64-linux Ludovic Courtès
2022-10-21 13:42         ` Efraim Flashner
2022-10-22 20:22         ` Efraim Flashner
2022-10-26  9:01           ` Efraim Flashner
     [not found]     ` <87h6zyo811.fsf@gnu.org>
2022-10-21  8:43       ` Status of armhf-linux and powerpc64le-linux Ludovic Courtès
2022-10-21  9:30         ` Mathieu Othacehe
2022-10-31 17:40         ` Tobias Platen
2022-10-22 12:18     ` Release progress, week 2 Christopher Baines
2022-10-25  9:50     ` Release progress, week 2, release manifest, what builds are failing? Christopher Baines
2022-10-25 11:29       ` Release progress, week 2, release manifest, what builds are failing: gst-plugins-bad Christopher Baines

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=87edvkc6am.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=guix-maintainers@gnu.org \
    --cc=julien@lepiller.eu \
    --cc=marius@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).