Closed
Bug 458056
Opened 17 years ago
Closed 17 years ago
shipped-locales update for Firefox 3.1 Beta 1
Categories
(Firefox :: General, defect, P1)
Firefox
General
Tracking
()
VERIFIED
FIXED
Firefox 3.1b1
People
(Reporter: Pike, Assigned: Pike)
Details
Attachments
(2 files)
465 bytes,
patch
|
Details | Diff | Splinter Review | |
622 bytes,
text/plain
|
Details |
We should update the shipped locales info in the tree for Firefox 3.1.
I'm wondering in which form we want to do that.
Updating shipped-locales, with a separate file for source stamps, or one file including both. A shipped-locales.ini like
[be]
SourceStamp=4aa0ee103fc7
[ja]
SourceStamp=d3e357c1d1ee
platforms=linux win32
[ja-JP-mac]
SourceStamp=c0977b38f38c
platforms=osx
would work for me, though that's somewhat tuning the world towards python scripting.
We could go for both for B1, and see which is better to work with. From the l10n process side, one file to transfer would be preferred.
When are we going to start the builds? I'd rather not give the final sign off if we're still off by a few hours. I heard stuff about metered landings today still, for example.
The current list of locales is at http://spreadsheets.google.com/pub?key=p65aJnudhiiNdkpeIh3d1Qw with the source stamps as handed in by the localizers, which is 35 locales long, including ja-JP-mac excluding en-US.
Comment 1•17 years ago
|
||
From a release standpoint we need a regular shipped-locales file (same format used for fx2 and 3), and a l10n-changesets file, probably generated with get-l10n-revs.
We've already got a bunch of code that relies on the shipped-locales format, and unless there's a reason to change it I don't think we should.
For the purposes of this bug and 3.1b1 can we update shipped-locales like we always do? I don't think day-before-builds-start is the right time to be implementing new configuration files.
Assignee | ||
Comment 2•17 years ago
|
||
Korean is in, patch for b1. l10n-changesets coming up next.
Assignee: nobody → l10n
Status: NEW → ASSIGNED
Assignee | ||
Comment 3•17 years ago
|
||
Assignee | ||
Updated•17 years ago
|
Comment 4•17 years ago
|
||
Comment on attachment 341476 [details]
[checked in] l10n-changesets
Is this the final version?
Assignee | ||
Comment 5•17 years ago
|
||
From all I know, yes, I don't have any changes in the pipeline right now.
I don't know how things would look next week, and I guess neither of us knows when we actually start the builds, so this comes with limited warranty.
Comment 6•17 years ago
|
||
Comment on attachment 341476 [details]
[checked in] l10n-changesets
Okay, I've checked this in. We'll update later if need be.
changeset: 389:87374e3f8d8e
Attachment #341476 -
Attachment description: l10n-changesets → [checked in] l10n-changesets
Assignee | ||
Comment 7•17 years ago
|
||
http://hg.mozilla.org/mozilla-central/rev/55366228f456 is the landing of shipped-locales. Marking FIXED
Status: ASSIGNED → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Updated•17 years ago
|
Keywords: checkin-needed
Target Milestone: Firefox 3.1 → Firefox 3.1b1
Comment 8•17 years ago
|
||
Verified list on ftp://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/3.1b1-candidates/build2/win32/
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•