This is a tracker bug for releasing Firefox 3 hi-IN. 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 build, you can find the latest run of compare-locales on http://l10n.mozilla.org/buildbot/compare/linux-langpack/11280. This shows a few errors, most of which aren't really real, but caused by a utf-8 BOM in the files. I have updated code that can ignore those, but that's not running on the l10n server yet. There was one real bug, showing on your tinderbox for windows, http://tinderbox.mozilla.org/showbuilds.cgi?tree=Mozilla-l10n-gl, a BOM in charset.mk, which I fixed and checked in. Please cvs update your copy at gl/toolkit/installler/windows. You can find the latest build on the l10n server on http://l10n.mozilla.org/dashboard/.

hrm. shoot, wrong bug. Compare-locales run is on http://l10n.mozilla.org/buildbot/compare/linux-langpack/11276, no bugs, no fixes on my side. Tinderbox is at http://tinderbox.mozilla.org/showbuilds.cgi?tree=Mozilla-l10n-hi-IN. Sorry.

Hi, now that we have your localization on a release process for Firefox 3.0.x, there are some changes to the tree rules for your localization. For any check-in to a directory affecting Firefox on cvs trunk, please file a bug, and attach a patch for the change (or set of changes). CC me and request approval1.9.0.3 (set the flag on the attachment to '?'). The minor number will change as we move through the releases. I or someone else from the l10n-drivers team will look at your patch and check for technical regressions, and if the patch approval will be granted (the flag will be changed to '+'). If the patch needs to be improved, it will get denied by setting the flag to '-'. Please follow up with a new patch addressing the comments. You shouldn't land any changes before the patch got approved on cvs trunk. This ensures that we have ship-ready code in the l10n repositories at all times, and can flexibibly respond to changes in the security area like zero-day exploits. Thanks for your help, and I hope that you get good feedback on your beta release. I'm turning over to the hg bugs for 3.1 next. After the initial commit, the hg repos will be open for changes, except search and region.properties, for which you should continue to track changes in bugs with stas and me on board, and reviewed patches.

Hindi is out of beta now. Closing this bug. Thanks to all for all the hard work!