Closed
Bug 838551
Opened 11 years ago
Closed 11 years ago
add support for 11 new b2g locales to mapper & repositories
Categories
(Release Engineering :: General, defect)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: catlee, Assigned: hwine)
References
Details
(Whiteboard: [re-b2g])
Attachments
(2 files)
2.73 KB,
text/plain
|
stas
:
review+
|
Details |
3.77 KB,
patch
|
nthomas
:
review+
hwine
:
checked-in+
|
Details | Diff | Splinter Review |
https://tbpl.mozilla.org/php/getParsedLog.php?id=19482084&tree=Mozilla-B2g18&full=1#error0 failed trying to look up http://hg.mozilla.org/gaia-l10n/el/rev/9fabe77b794d at http://cruncher.build.mozilla.org/mapper/l10n/git/9fabe77b794d which current returns {"git_rev": null} Looks like we're not mirroring the 'el' revision in git.
Assignee | ||
Comment 1•11 years ago
|
||
Correct. We've received no request that Greek be part of an official build. Only shipping locales are supported at this time. I'll investigate
Assignee | ||
Comment 2•11 years ago
|
||
Confirmed with Stas in #l10n that 'el' was added. Along with 10 others. See https://github.com/mozilla-b2g/gaia/commit/fd41681a3b52f2be790b257cbee9fe9c2fc2732c#diff-4 for details. Next steps: 1) add the conversion of the 11 to vcs-sync, including mapper support 2) add the repositories to git.mozilla.org 3) publish to git.mozilla.org The build process will stop failing after #1 is completed. All 3 steps need to be completed before partners will be able to replicate builds.
Summary: Missing l10n revisions in mapper (missing for 'el' locale) → add support for 11 new b2g locales to mapper & repositories
Whiteboard: [re-b2g]
Assignee | ||
Updated•11 years ago
|
Assignee: nobody → hwine
Status: NEW → ASSIGNED
Assignee | ||
Comment 3•11 years ago
|
||
Please confirm this is the correct set of hg repos to use for b2g
Attachment #710812 -
Flags: review?(stas)
Comment 4•11 years ago
|
||
Comment on attachment 710812 [details] list of hg repos supporting locales >cs: http://hg.mozilla.org/gaia-l10n/cs >cs: http://hg.mozilla.org/l10n-central/cs >cs: http://hg.mozilla.org/releases/l10n/mozilla-aurora/cs >cs: http://hg.mozilla.org/releases/l10n/mozilla-beta/cs >cs: http://hg.mozilla.org/releases/l10n/mozilla-release/cs The list looks good, but I'm not sure abut the Gecko part. Axel, do we need all four channels' repos?
Attachment #710812 -
Flags: review?(stas)
Attachment #710812 -
Flags: review?(l10n)
Attachment #710812 -
Flags: review+
Comment 5•11 years ago
|
||
Comment on attachment 710812 [details]
list of hg repos supporting locales
Removing the r? request on Axel. Hal tells me this is for consistency: only one of the Gecko repos is migrated to git's master, others are mapped into branches.
Attachment #710812 -
Flags: review?(l10n)
Assignee | ||
Comment 6•11 years ago
|
||
Update: (In reply to Hal Wine [:hwine] from comment #2) > Next steps: > 1) add the conversion of the 11 to vcs-sync, including mapper support > > The build process will stop failing after #1 is completed. All 3 steps need > to be completed before partners will be able to replicate builds. Step 1 has been completed, builds using the new locales will complete now.
Assignee | ||
Comment 7•11 years ago
|
||
All repos just updating and converting for now to feed the mapper.
Attachment #711088 -
Flags: review?(nthomas)
Comment 8•11 years ago
|
||
Comment on attachment 711088 [details] [diff] [review] new l10n repos into conversion automation This makes me wonder if we should be doing gecko for all the first set of locales too.
Attachment #711088 -
Flags: review?(nthomas) → review+
Assignee | ||
Comment 9•11 years ago
|
||
Comment on attachment 711088 [details] [diff] [review] new l10n repos into conversion automation landed: http://hg.mozilla.org/users/hwine_mozilla.com/repo-sync-configs/rev/c038594e1cb0 and deployed
Attachment #711088 -
Flags: checked-in+
Assignee | ||
Comment 10•11 years ago
|
||
All gaia & beta gecko repos being pushed to git.mozilla.org now as part of automation.
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
Updated•7 years ago
|
Component: Tools → General
You need to log in
before you can comment on or make changes to this bug.
Description
•