REMINDER: Release 3.4.0-beta5 from libreoffice-3-4 branch

l10n
#1

Hi,

there were again some problems with localizations[*] in beta4, so we
decided to release beta5 instead of rc1 this week. The commit deadline
is today.

Commit rules for libreoffice-3-4 branch after May 9, 2011:

  + all commits need one review, ask on irc or
          libreoffice@lists.freedesktop.org mailing list
  + do not modify strings or UI
        + commit only safe bug fixes

For more deadlines see
http://wiki.documentfoundation.org/ReleasePlan#3.4.0_release

[*] Please, be patient. There were big changes in the build framework
between LO-3.3 and 3.4. We stopped using obsolete helper scripts from
the build repo. Started building many modules using GNU make instead of
dmake. Started building from PO files instead of the generated SDF
files. Installed some new build hosts. It brought some unexpected
problems but we all improving it. Also there was a problem with
communication when developers were not aware of the problems on Linux.
We are all hardly working on it and learning from mistakes. Every beta
is more and more usable.

Note that we really want to use the time based schedule. See also the
updated http://wiki.documentfoundation.org/Release_Criteria

Best Regards,
Petr

#2

2011.05.09. 18:36 keltezéssel, Petr Mladek írta:

Commit rules for libreoffice-3-4 branch after May 9, 2011:

  + do not modify strings or UI

First I wanted to write that how lucky we were, that we had been
effectively in string freeze since April 11. Unfortunately string freeze
was broken by
http://cgit.freedesktop.org/libreoffice/libs-core/commit/?h=libreoffice-3-4&id=ad50ce46a6a25f73b7a1a1f69eb17e777e28cc22
4 days ago. I'm thinking of the best solution. Last time it took 3 days
to update Pootle. :frowning: For a single "Find" which is duplicated in several
copies elsewhere in translations it is probably an overkill.

Please continue with translation fixes and completition.

Thanks,
Andras

#3

Joop Kiefte píše v Po 09. 05. 2011 v 13:39 -0300:

hardly working > working hard, I suppose... I'm hardly working = I'm
doing almost nothing...

Heh, "working hard" is what I wanted to say. We are still far from
holidays :wink:

Best Regards,
Petr

#4

Hi Petr,

Hi,

there were again some problems with localizations[*] in beta4, so we
decided to release beta5 instead of rc1 this week. The commit deadline
is today.

Thanks a lot!

Commit rules for libreoffice-3-4 branch after May 9, 2011:

  + all commits need one review, ask on irc or
           libreoffice@lists.freedesktop.org mailing list
  + do not modify strings or UI
         + commit only safe bug fixes

For more deadlines see
http://wiki.documentfoundation.org/ReleasePlan#3.4.0_release

[*] Please, be patient. There were big changes in the build framework
between LO-3.3 and 3.4. We stopped using obsolete helper scripts from
the build repo. Started building many modules using GNU make instead of
dmake. Started building from PO files instead of the generated SDF
files. Installed some new build hosts. It brought some unexpected
problems but we all improving it. Also there was a problem with
communication when developers were not aware of the problems on Linux.
We are all hardly working on it and learning from mistakes. Every beta
is more and more usable.

Yes, I think that we all know that a lot is going on and that we need to adapt ourselves to this new process too.

Note that we really want to use the time based schedule. See also the
updated http://wiki.documentfoundation.org/Release_Criteria*

Thanks again for your quick reaction on the localization issue and providing another beta.

Kind regards
Sophie

#5

Andras,

2011.05.09. 18:36 keltezéssel, Petr Mladek írta:

Commit rules for libreoffice-3-4 branch after May 9, 2011:

+ do not modify strings or UI

First I wanted to write that how lucky we were, that we had been
effectively in string freeze since April 11. Unfortunately string freeze
was broken by
http://cgit.freedesktop.org/libreoffice/libs-core/commit/?h=libreoffice-3-4&id=ad50ce46a6a25f73b7a1a1f69eb17e777e28cc22
4 days ago. I'm thinking of the best solution. Last time it took 3 days
to update Pootle. :frowning: For a single "Find" which is duplicated in several
copies elsewhere in translations it is probably an overkill.

It is very simple. This person must be told that string freeze was on
May 2 and his fix from May 5 will be deleted and excluded from LO34.

No matter that he comes from Novell. Or is Novell now like Sun/Oracle
in the OOo, they can do whatever they please, no matter when the
deadlines and freezes are?

This should really be a no brainer.

Lp, m.
Martin

#6

hardly working > working hard, I suppose... I'm hardly working = I'm
doing almost nothing...

#7

Andras,

2011.05.09. 18:36 keltezéssel, Petr Mladek írta:

Commit rules for libreoffice-3-4 branch after May 9, 2011:

+ do not modify strings or UI

It is very simple. This person must be told that string freeze was on
May 2 and his fix from May 5 will be deleted and excluded from LO34.

It's not that easy, Petr has just extended to string freeze deadline
to May 9. :slight_smile: It's a rubber deadline, it seems. :slight_smile:

No matter that he comes from Novell. Or is Novell now like Sun/Oracle
in the OOo, they can do whatever they please, no matter when the
deadlines and freezes are?

This should really be a no brainer.

What I did not like in the Sun/Oracle era that we were heavily bound
by their rules. TDF does it more relaxed and I fully support it. In
this very case, the translation of string "Find" can be found in the
same PO file multiple times (one for Calc, one for Writer etc.) It is
a no brainer to add "Find" and its translations for the Basic IDE,
too, and it poses no risk at all. Translators do not have to do
anything.

Best regards,
Andras

#8

Andras Timar wrote (09-05-11 21:17)

2011.05.09. 18:36 keltezéssel, Petr Mladek írta:

Commit rules for libreoffice-3-4 branch after May 9, 2011:

       + do not modify strings or UI

It is very simple. This person must be told that string freeze was on
May 2 and his fix from May 5 will be deleted and excluded from LO34.

It's not that easy, Petr has just extended to string freeze deadline
to May 9. :slight_smile: It's a rubber deadline, it seems. :slight_smile:

And the commit was a bugfix.. or should that not make any difference?

Cor

#9

Hi *,

Andras Timar wrote (09-05-11 21:17)

[...]

It is very simple. This person must be told that string freeze was on
May 2 and his fix from May 5 will be deleted and excluded from LO34.

It's not that easy, Petr has just extended to string freeze deadline
to May 9. :slight_smile: It's a rubber deadline, it seems. :slight_smile:

And the commit was a bugfix.. or should that not make any difference?

I don't see it as critical/problematic. Yes, in OOo-times this would
be a disaster, as it would take ages until the changed strings are
made available to translators, and again take ages until the
translator's updates get integrated into the build.

But when you have your translations update for each build (and you
more or less get a new build each week), a fix in the english string
is not a bad thing..

Yes, some langs might not be able to do it for the next build, but
then it just will go int the one after the next..

ciao
Christian