February 25, 2009

Accesskey improvements in the Thunderbird preferences window

I just pushed a fix for bug 453256 to the comm-central repository.

What this fix does, is to take advantage of the fix for bug 143065, to make sure that the accesskeys that we use in the Display, Composition, Privacy, and Advanced prefpanes are now much more sane, than they used to.

Prior to this fix accesskeys were shared across all tabs, so that if Advanced/General used "A" for "Automatically..." then Advanced/Update couldn't use A as an accesskey. That resulted in a lot of inadequate accesskey choices.

So dear localizers: If you haven't already taken advantage of the fix for bug 143065, please do so now and improve your accesskey story in the Thunderbird preferences window.

February 23, 2009

Thunderbird 3 Beta2 l10n update

We're in the last stages of the beta2 release cycle for Thunderbird 3, after some last minute l10n checkins. And the good news is that we have more and more locales on board. We will release beta2 in 43 languages, five more than what we achieved with beta1.

Looking back at the whole Thunderbird 3 release cycle, we see a steady increase:
  • Thunderbird 3 alpha1: 1 language
  • Thunderbird 3 alpha2: 12 languages
  • Thunderbird 3 alpha3: 28 languages
  • Thunderbird 3 beta1: 38 languages
  • Thunderbird 3 beta2: 43 languages
This is a great achievement, given that we released Thunderbird 2 with only 38 languages. I want to thank all our localizers for making this happen. I'm now pretty optimistic about breaking the 50 languages barrier in the final Thunderbird 3 release later this year.

Unfortunately we are missing three locales in the beta2 release that were included in the beta1 release, but hopefully we can pick those up again with our next release (beta3) or our final release.

February 17, 2009

All Thunderbird strings are now frozen for the beta2 release

I just wanted to remind everyone that as of last night, Tuesday, February 17 at 23:59 PST, the firm code and string freeze went into effect. That means that all strings are now entirely frozen until we release Thunderbird 3 beta2.

As of now 28 locales have already opted-in to be part of this release. An additional 9 locales are green (meaning that they have no missing strings in their localization) on our l10n dashboard and will hopefully opt-in soon. Hopefully even more will follow so that Thunderbird 3 beta2 will be the largest release in terms of the number of localized versions ever.

If you want be part of this release, please opt-in in the corresponding opt-in thread in the mozilla.dev.l10n newsgroup.

One additional note to localizers:
Please take a close look at the status of your tinderbox (at http://tinderbox.mozilla.org/showbuilds.cgi?tree=Mozilla-l10n-locale where "locale" must be replaced with your locale code (e.g. es-ES or de). I've seen some locales having a red Windows tinderbox, because those locales didn't follow this change to our installer strings. Please check if this applies to you and make the necessary changes before opting-in.

February 12, 2009

Thunderbird 3 beta2 slushy string freeze in effect

Some of you have probably already noticed, but for those who didn't:

Since Tuesday, 23:59 Pacific Time we're in the so-called slushy string freeze for TB3 beta2. "Slushy" in this context means that from that date on only string changes in blocker bugs will be accepted (and marked as late-l10n) until the firm string freeze next Tuesday, Feb 17 23:59 PST.

Unfortunately we screwed up a little bit shortly before the slushy string freeze date by committing some string-only patches. Something the introduction of the "slushy" period was intended to fix.

The downside of this is that some strings were introduced which might be hard to translate because the UI is still missing for those. The upside is, that because of that we don't have any more blockers left with a potential string impact, so the risk of late-l10n changes is pretty slim.

So please start your work now, if you did not already.

I'll also start an opt-in thread shortly in the mozilla.dev.l10n newsgroup.

February 6, 2009

REMINDER: String freeze for Thunderbird 3 beta2 in four days

Just as a heads up for everyone involved. We're getting nearer to our two proposed string freeze dates. The first date, the so-called "slushy string freeze" will be on Tuesday, February 10 23:59 pacific time. We hope to have all blocker bugs with string impact done by this date. I've talked with the Thunderbird developers about this and they have told me that they will make an effort to get all of those bugs done by next Tuesday.

There's a second line of defense as well, that being our firm string freeze on Tuesday, February 17 23:59 pacific time. All of the bugs with l10n impact that aren't fixed by then and any potential late-l10n bugs will have to be fixed by that date to make the release.

From that point on, localizers will have two full days until Thursday, February 19 23:59 pacific time to get their localization in shape and opt-in for the beta2 release. After that date, we will start with testing our candidate builds and hopefully release Thunderbird 3 beta2 on Tuesday, February 24.

We know that this is a tight schedule, so we believe it would be a sensible approach for all localizers to start working on the remaining missings strings after the "slushy string freeze" and not to wait with all the remaining until the firm freeze.

Let me know what your thoughts are on this.