I wish you all a happy new year, and a whopping Firefox 3.1.
* Frozen. That means that developers need to wrestle down Mike Beltzner
and explain why they didn't know in time that they needed more strings,
and that we really can't ship 3.1 without it.
** In the dev meeting on Tuesday, the js group raised concerns about the
code freeze. They didn't wrestle beltzner down yet, but they're still
working on it. Don't assume you get more time for B3, though you might.
dev-l10n mailing list
[hidden email] https://lists.mozilla.org/listinfo/dev-l10n
What should new locales who want to target Beta 3 as their first Beta
release do? fx31fa is green on the dashboard, and Tinderbox builds
also succeed. We're in the process of testing the localization, and
we'd be ready to target Beta 3 as fa's first beta release. Please let
us know if we need to do something other than what you listed here as
a new locale.
> Hi all,
> Strings for Firefox 3.1 are frozen [*], and code freeze for Beta 3 is in
> a week from now (-2 hours), January 13th, 11:59pm PDT [**].
> Please make sure that your fx31x trees onhttp://l10n.mozilla.org/dashboard/?tree=fx31xare green, and that your
> builds on tinderbox succeed, the "Firefox mozilla-1.9.1 ..." count. They
> can be found onhttp://tinderbox.mozilla.org/showbuilds.cgi?tree=Mozilla-l10nandhttp://tinderbox.mozilla.org/showbuilds.cgi?tree=Mozilla-l10n-ab-CD. If
> your locale doesn't show those columns, that's because they only build
> on push, and drop off the display after 12 or 24 hours.
> The generated builds are onhttp://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-mozilla....
> Try to get as much pre-release testing to those builds as you can, this
> is going to be our last Beta, and our most popular one.
> When you're done and ready for Beta 3, please follow up on this thread,
> with your locale code and revision onhttp://hg.mozilla.org/releases/l10n-mozilla-1.9.1/ab-CD/.
> Useful documents:https://developer.mozilla.org/en/L10n_on_Mercurialhttp://groups.google.com/group/mozilla.dev.l10n/browse_frm/thread/a49...
> I wish you all a happy new year, and a whopping Firefox 3.1.
> * Frozen. That means that developers need to wrestle down Mike Beltzner
> and explain why they didn't know in time that they needed more strings,
> and that we really can't ship 3.1 without it.
> ** In the dev meeting on Tuesday, the js group raised concerns about the
> code freeze. They didn't wrestle beltzner down yet, but they're still
> working on it. Don't assume you get more time for B3, though you might.