Closed Bug 446608 (fx3-l10n-mr) Opened 14 years ago Closed 13 years ago

[mr] Firefox 3 release tracker Marathi

Categories

(Mozilla Localizations :: mr / Marathi, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: Pike, Unassigned)

References

Details

This is a tracker bug for releasing Firefox 3 mr.

This bug is not that detailed, but as we get particular work items, they should
block this bug for tracking, and better discoverability.
Alias: fx3-l10n-mr
Depends on: 446609
Depends on: 446612
Depends on: 446613
Depends on: 446614
Depends on: 446615
Depends on: 446617
Depends on: 428190
[mr] Marathi status as of now:

1) http://tinderbox.mozilla.org/showbuilds.cgi?tree=Mozilla-l10n-mr reveals,  tree: Mozilla-l10n-mr is healthy (at-least for Linux and Mac OSX).

2) Following Depends on bugs have status:
RESOLVED FIXED:  446609, 446613 & 446614

3)Following Depends on bugs have status:
NEW: 428190, 446612, 446615 & 446617

Necessary action items (in form of comments) and/or patches have been submitted for above bugs (428190, 446612, 446615 & 446617).

Thereby, wondering  whether bugs (428190, 446612, 446615 & 446617) have reached Status: RESOLVED FIXED   or  any input is still required from my side wrt [mr] Firefox 3 release ?
[mr] quick update:

1) http://tinderbox.mozilla.org/showbuilds.cgi?tree=Mozilla-l10n-mr reveals, 
tree: Mozilla-l10n-mr is healthy for following build families i.e.
a. Linux
b. Mac OSX 
c. Windows 
 
2) Pike, thanks for pointers wrt change in variable name in l10n/mr/browser/installer/override.properties and thereby maintaining tinderbox green consitently for tree: Mozilla-l10n-mr.
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.
We're shipping mr 3.0.x as regular release, marking this bug FIXED.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.