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

Hi,

First of all, thanks.  And second, to leave a clear statement about the
main point: I agree with your proposed time frame for the string freeze,
October 26th (freeze) to 29th (release).

zimoun <zimon.toutoune@gmail.com> writes:
> Maybe I am missing something.

Probably this context helps: I've already uploaded to TP the translation
for the manual, so I can compare the "old" pot (the one uploaded to TP)
with the "new" one (the one I generated today on my machine).

> 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 :-)).

Nobody likes deadlines---at least not me, hehe---but I believe they can
be really useful sometimes. :-)

> The last week, we could string freeze for polishing and not run after
> an always moving target.

Yup, that's the main advantage of freezing: you can focus as much as
possible on the little and not so little details, like bug hunting.

> 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?

I agree that a longer string freeze wouldn't a big difference, and even
may hurt.  At least the manual is a huge work that probably cannot be
done in weeks from scratch, so I'm not thinking about the string freeze
as "the time frame to perform the translation" but "a time frame to
check the translation already done and fix last minute issues/features".

Besides, sorry if the word 'tight' sounded as a complaint meaning
protest, if so it'd really be a complaint meaning grief for my schedule,
as I'm unable to dedicate much time on working days.

Happy hacking and translation too!
Miguel


  reply	other threads:[~2020-10-12 21:27 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
2020-10-12 21:26             ` Miguel Ángel Arruga Vivas [this message]
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=87v9ff16ha.fsf@gmail.com \
    --to=rosen644835@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 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).