This is a tracker bug for releasing Firefox 3 ml. This bug is not that detailed, but as we get particular work items, they should block this bug for tracking, and better discoverability. This is currently blocked by branching for Firefox 2, marking that dependency.

Added to the fx3 build as we resolved fx2 WONTIFX in favor of this. You can find the latest compare-locales run on http://l10n.mozilla.org/buildbot/compare/linux-langpack/11279, and the currently latest one via the dashboard, as usual. There's a tinderbox now, too, you find that at http://tinderbox.mozilla.org/showbuilds.cgi?tree=Mozilla-l10n-ml

Updating the summary, alias and dependencies - we're targeting 3.1 here, not 3.0.

Have commented on all the four dependancy bugs: 475016, 475017, 475018, 475020

Morphing this bug into a version-independent tracker.

Firstly, congratulations team! You have worked and managed to get all the dependencies for this bug fixed, which means that productization for Malayalam Firefox is all done. Please take a minute or two and read the next steps to follow. == Aurora == Every 6 weeks, we will update aurora repositories with new strings that will require some additional time spent on it. As you probably already know, we advise all localizers to use Aurora channel for all translations, so that we can merge them with Beta channel when needed without any regressions. So, please use Aurora as your primary working repo, and in case you're landing a fix to Beta channel, please port it back to Aurora too. Once the Aurora builds are available, please use them as much as you can for the purpose of testing your own translations and making sure everything is as it should be. == Bugs == Please check your dashboards every now and then to see if there are some bugs filed against Firefox Malayalam. You can check the status of your latest builds and some team info on l10n dashboard teams page at https://l10n-stage-sj.mozilla.org/teams/ml . As the website evolves, you'll start using that as your primary source of info related to localization. One other important thing to have in mind is webdashboard. We use webdashboard to show contributors bugs related to web localization for their locale. This is really important as we use our websites to promote localized Firefox builds. == Staying connected == You should also follow the Mozilla l10n newsgroup, http://www.mozilla.org/community/forums/#dev-l10n, available as mailing list, newsgroup or google group. The traffic isn't too high frequency. You'll find all announcements at http://www.mozilla.org/community/forums/#dev-l10n-announce . Those are vital to read, as they include things that the l10n-drivers want you to know and attend to. There's a third group, http://www.mozilla.org/community/forums/#dev-l10n-web, where we discuss web localization issues. That's a separate group as quite a few localization teams have dedicated volunteers for that. Another important thing is staying in touch with community and make yourself available for anyone who wants to contribute. So, if possible, get in touch with community on community forums, get feedback and possibly more volunteers. Enjoy and congratulations!