unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: "Miguel Ángel Arruga Vivas" <rosen644835@gmail.com>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Release v1.2 and Translation
Date: Mon, 12 Oct 2020 21:49:05 +0200	[thread overview]
Message-ID: <CAJ3okZ3CWdh81jq-OPxJQsgVNaDSLDsFAat7NL6BGncx5EKrxg@mail.gmail.com> (raw)
In-Reply-To: <877drv2zeq.fsf@gmail.com>

Dear,

On Mon, 12 Oct 2020 at 18:16, Miguel Ángel Arruga Vivas
<rosen644835@gmail.com> wrote:

> > From my point of view, a string freeze starting on Mon. Oct. 26th
> > seems the easiest to synchronize all etc.
> > And unfreeze once the branch is create &co.
>
> Three days is a tight schedule, but could be enough if the number of
> changes keeps close to the current one (there are already 98 fragments
> without translation on guix-manual, none on guix and I didn't check
> guix-packages).

Maybe I am missing something.  Now the translation 1.2.0-pre1 is open,
so it is almost 3 weeks (even if I know it is maybe not enough, well
we have to fix some deadlines somehow :-)).
The last week, we could string freeze for polishing and not run after
an always moving target.
From my point view, a longer freeze would not help to have the work
done.  I do not know.  What do you think it could be better?

All the best,
simon


  reply	other threads:[~2020-10-12 19:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-09  9:23 Release v1.2 and Translation zimoun
2020-10-09 12:04 ` Julien Lepiller
2020-10-11 19:20   ` Miguel Ángel Arruga Vivas
2020-10-12 12:28     ` Ludovic Courtès
2020-10-12 13:05       ` zimoun
2020-10-12 16:15         ` Miguel Ángel Arruga Vivas
2020-10-12 19:49           ` zimoun [this message]
2020-10-12 21:26             ` Miguel Ángel Arruga Vivas
2020-10-19 16:23               ` zimoun

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=CAJ3okZ3CWdh81jq-OPxJQsgVNaDSLDsFAat7NL6BGncx5EKrxg@mail.gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=rosen644835@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).