[ANNOUNCE] String freeze in effect for Thunderbird 3 beta1 release

[Simon Paquet]

Hi guys,

I want to inform you that as of midnight Pacific time yesterday (roughly
six and a half hours ago) were in string freeze for the Thunderbird 3
beta1 release.

This means that any l10n strings in the mail/ and editor/ui/ directories
in the comm-central repository are now frozen. Since Firefox is also in
string freeze for it 3.1 beta2 release right now the strings in browser/,
dom/, netwerk/, security/manager/ and toolkit/ are frozen as well. So we
don't need to worry about any breakage that might come from that front.

The code freeze for our beta 1 will be on Tuesday 18th November at
23:59 Pacific time. We'll cut the release sometime after that once we've
had some baking. So this means basically that your locales should be
ready by that date. I'll open up a opt-in thread for you guys as soon as
the code freeze is in effect.

We will be having a test day for beta 1 soon, that will be covering the
new features and checking for any significant regressions. More details
coming soon.

Please check the dashboard http://l10n.mozilla.org/dashboard/?tree=tb30x
for up-to-date information on the state of your locale. We also have l10n
nightly builds available at the regular location
http://ftp.mozilla.org/pub/mozilla.org/thunderbird/nightly/latest-comm-central-l10n/

Cya
Simon
--
Thunderbird/Calendar Localisation (L10n) Coordinator
Calendar website maintainer: http://www.mozilla.org/projects/calendar
Calendar developer blog: http://weblogs.mozillazine.org/calendar

[David Bienvenu]

We are in string freeze, but there will be a few additional bugs landed
that require new strings, before beta 1. So we will be managing these by
exception.

I landed one this morning,
https://bugzilla.mozilla.org/show_bug.cgi?id=455978

I believe https://bugzilla.mozilla.org/show_bug.cgi?id=456818 will
require a new string (dmose can correct me if I'm wrong)

https://bugzilla.mozilla.org/show_bug.cgi?id=429843 may require a few
new strings.

Also, we decided last night that we're not going to be at 0 beta 1
blocker bugs by Nov. 18th, so we will be slipping the beta 1 code freeze
date by a few days. We're going to evaluate where we are with the
blocker list early next week and try to set a new code freeze date at
that point.

- David

[Emre Birol]

Also, I like to add the following one to the list below;

https://bugzilla.mozilla.org/show_bug.cgi?id=464784

It contains a single string.

[Simon Paquet]

Emre Birol wrote:

>Also, I like to add the following one to the list below;
>
>https://bugzilla.mozilla.org/show_bug.cgi?id=464784
>
>It contains a single string.

I would (and will) oppose giving this bug late-l10n status. As said
elsewhere, late-l10n bugs should be an exception. The keyword is for
bugs that come up *after* the string freeze, but are very important/
critical for the release and need to be fixed ASAP.

None of this applies to this bug. This can (and should) go in after beta
1. There's no need for us to push 30+ localizers to fix this within a
very short timeframe.

Simon Paquet