String Freeze for Lightning 1.0b2 Release Today

I want to make those of you, who are actively translating Lightning aware, that we are now ready to freeze our strings for the approaching 1.0b2 release.

After the string freeze we are currently planning for two and a half additional weeks before we try to release our first release candidate on May 25th. We would really appreciate it if you could have your locales in shape for the first RC, as I do hope we will only need one release candidate. Please also note that we have to stay in sync with the Thunderbird schedule, so we might have to prepone our rc1 release to an earlier date.

That gives you 2-3 weeks to get your localizations in shape.

The 1.0b2 release will come from the comm-1.9.2 release branch, which means you should commit your work to the l10n-mozilla-1.9.2 repositories. If any of you will not be able to keep his or her locale updated for the 1.0b2 release, please let me know beforehand.

I am aware that we still don’t have bug 346278 fixed, I am really sorry this is still the case. If rc1 is released and you notice any localization problems, please do let me know as quickly as possible so I can coordinate a second release candidate. I do hope to fix this bug in the next two weeks though!

Please let Simon Paquet or me know if any of you wants to join us for 1.0b2.

If you have any questions, please do not hesitate to ask them here


Update: It seems the calendar10x dashboard is not correctly updated. Please use the latest version of the dashboard to find out how many strings are missing!

Comments are closed.