L10n:Official Localized Releases

Official Build

An L10n official build means that:

1- Mozilla Corporation resources handle minor updates, etc and collaborates with you to complete a release. More specifically,

An approval for change requests is led by Axel
Code/string/catch ups are also approved by Axel
Branding changes (e.g., search, RSS, content handlers) are approved by Mic
Changes to in product web pages are approved by Pascal

2- Your team may not have a what we call a "full-skills team". Meaning all the building blocks for supporting your localization. [mic note insert note to get to Building blocks]. Mozilla is working to develop more ways to support you to develop your building blocks. Check out Seth's blog to hear more about our ideas.

3- Major updates are done by you. Our next major update is Firefox 3

Here are some tools that are likely going to be useful for you in this stage.
There are occasions when localizers don't meet the ship deadlines, we try to do everything we can to support you to meet the release dates. Mozilla (we) does this by communicating well in advance of deadlines and being clear about module owners and the like. In the case where a deadline is going to be missed, we've considered these as our suggested options:
next release as acceptable
special cases we may create a delay on being official build status

We're working on better understanding the state of your building blocks, meaning the size of your team (if you have one), where you might need help so that we can better support you. We've recently invested more resources to better support your community development efforts. If you feel your team is need of this type of support please email us.

[Mic note: insert how do we assess the "health" of a localization team and how we could better support them to develop their team or their skills].

4-Mozilla supports the quality assurance testing of your build

We've instituted a new testing platform and protocols to better support this for Firefox 3
We've also created a 2-week code freeze before Beta 2 to ensure you have sufficient time to implement new changes
And, we've created new tools [Axel help here] to provide nightly builds for which you can test your work against and have more dynamic results