get a compare-locales version for production machines to use

VERIFIED FIXED

Status

P2
normal
VERIFIED FIXED
10 years ago
5 years ago

People

(Reporter: armenzg, Assigned: coop)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

10 years ago
When we will want to have compare-locales for mozilla-central (since for 1.9.0 will not be blocking as per call with Axel) we should be able to find something figured out.

There is one version of compare-locales in:
http://hg.mozilla.org/users/axel_mozilla.com/tooling/file/tip/mozilla/testing/tests/l10n/

What there is in CVS has not had work on it since December 2007 and has fall behind from Axel's development
http://mxr.mozilla.org/mozilla/source/testing/tests/l10n/

As per conversation with Axel; Gandalf and Adrian are doing some more development on it

I want to use this bug as way of keeping the other two compare-locales related bugs in context
There is another compare-locales script, activly developed by Adrian right now.

He's merging Axel's compare-locales with Silme library. The good thing about it is that Silme does cover pretty nice list of features that you may want to extending compare-locales shouldn't be a problem.

All is down to what do you need.

http://hg.mozilla.org/users/akalla_aviary.pl/silme-patched/file/0207a01d1b99/scripts/compare-locales2.py

Comment 2

10 years ago
We shouldn't bother the rel-eng team with the silme version until it's ready for production.
Pike: roger that

Comment 5

10 years ago
updating revision to http://hg.mozilla.org/users/axel_mozilla.com/tooling/file/487d597612fd/compare-locales/

l10n-merge doesn't work for defines files, so I had to disable that. Discovered that while working on bug 461979.

Updated

10 years ago
Component: Release Engineering → Release Engineering: Future

Comment 6

10 years ago
What does moving this status to RelEng: Future mean?  It seems to be very important for the l10n community to have a working version of compare-locales in the build process.  Not sure when "future" means, but I would like to have this back to a closer time frame.  Can someone provide clarity?  How long is "future"?

If it seems helpful, I am happy to arrange a discussion about why compare-locales is important to all the localization teams?
(Reporter)

Comment 7

10 years ago
Seth, currently compare-locales is being run on the l10n-dashboard which localizers look at and they will still be able to look at that output over there.

Currently there is not a maintained compare-locales in our repos and the newer python version that is maintained, it currently lives in pike's repo.
To run code that has not been reviewed in the release machines could lead us to unknown problems during a release.
You can also check this bug 458938 for more info
(Assignee)

Updated

10 years ago
Component: Release Engineering: Future → Release Engineering
Priority: -- → P3

Updated

10 years ago
Blocks: 470673
(Assignee)

Updated

10 years ago
Assignee: nobody → ccooper
Status: NEW → ASSIGNED
(Assignee)

Comment 8

10 years ago
Axel: is the revision in comment #5 still the most up-to-date? I'd like to start reviewing.
Priority: P3 → P2

Comment 9

10 years ago
Yes, compare-locales 0.6.1 of comment 5 is still current.

There is a slight nit in http://hg.mozilla.org/users/axel_mozilla.com/tooling/rev/b2fc94a2af23, which fixes a bug for the l10n builds setup.

tip is essentially just as good right now for you, too. The differences are only affecting the other sub parts.
(Assignee)

Comment 10

10 years ago
I've merged Axel's compare-locales into http://hg.mozilla.org/build/tools. I removed the web/ subdir since Axel tells me that's no longer used. I'll want to add some comments to the compare-locales libs (class descriptions and such) but those become commits regardless of which repo we're dealing with.

Axel: can you start working from this new repo, assuming I didn't miss anything? It was a trivial merge, so I don't expect any issues.

We'll use the current tip (changeset: 225:db705930f780) for build steps until Axel's tells us a new changeset is ready for testing. 

Note that this code is not yet being used in build steps. I'll file a new bug shortly to hook this code up to Armen's repack-on-change work (bug 464163).
(Assignee)

Updated

10 years ago
Blocks: 478436
(Assignee)

Updated

10 years ago
Depends on: 479851
(Assignee)

Comment 11

10 years ago
compare-locales has been moved to its own repo to facilitate development independent of the other build tools:

http://hg.mozilla.org/build/compare-locales/

Sorry for polluting the build/tools repo with bogus history. :/
Status: ASSIGNED → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → FIXED

Comment 12

10 years ago
http://hg.mozilla.org/users/axel_mozilla.com/tooling/rev/d1c2d7d0afdc is the corresponding landing in my tooling repo, build/compare-locales it is from now on.
Status: RESOLVED → VERIFIED
No longer blocks: 470673
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.