As of tonight (April 3rd) at Midnight PDT, SeaMonkey will be locked under string freeze.

I was tempted to spin builds tonight for our b3 with l10nMerge, but I decided after skimming the l10n dashboard and seeing the number of strings that landed in our tree this past week (not to mention today), that I will tag/spin builds for beta3 Monday evening, around 9pm PDT or a bit later.

Consider this a request to update locales/request further sign off, etc.

We are basing SeaMonkey 2.1b3 against Gecko 2.0 (mozilla-2.0) for those of you who wish to build locally to test.

After tonight, we expect aproximately a month until 2.1 final, and en-US will remain frozen for SeaMonkey.

If there is a strong need for any en-US string changes, those will be evaluated on a case-by-case basis, with very strong reasons needed to accept. If we do chose to accept, I'll send along an l10n-note to this newsgroup.

The l10n tree we are using is the mozilla-2.0 l10n tree. Though the suite/ specific l10n files should be usable for comm-central-trunk (SeaMonkey 2.2) as well at the moment.

Followup-To set to m.d.l10n, if there are any questions feel free to contact me there.

--
~Justin Wood (Callek)
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey

Reply via email to