415575 - (fx3-l10n-bn-IN) Firefox 3 bn-IN release tracker

Status: RESOLVED FIXED

(Mozilla Localizations :: bn-IN / Bengali (India), defect)

Description

[Axel Hecht [:Pike]]

This is a tracker bug for releasing Firefox 3 bn-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 blocked on actually branching Fx 2 bn-IN for starters. Filing this now anyways.

Comment 1

[Axel Hecht [:Pike]]

Added to the build, fx3 bugs are coming up later, pushed back due to all meetings this week.

The latest compare-locales run is found via the dashboard, currently it's http://l10n.mozilla.org/buildbot/compare/linux-langpack/11272. There's a tinderbox now, too, at http://tinderbox.mozilla.org/showbuilds.cgi?tree=Mozilla-l10n-bn-IN.

Check-ins to fx3 are open, builds should run as you're used to.

Comment 2

[Runa Bhattacharjee]

Current Status for bn_IN is:

* All merges done to ensure that they locale folder in consistent
* 70% of the translations are done, rest in underway
* Webpages are being translated locally.

Looks good to make it for Friday.

Should i Accept this bug to get it assigned to me?

Comment 3

[Axel Hecht [:Pike]]

Sounds good.

Comment 4

[Runa Bhattacharjee]

Any updates on the status for the release? The Web parts bug (bug #443625) is still open and I am not sure if the patches in there have been accepted.

Comment 5

[Axel Hecht [:Pike]]

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.

Comment 6

[Staś Małolepszy :stas]

Marking as fixed. Bengali moved out from beta in 3.0.5. Congrats Runa! :)