bugzilla.mozilla.org will be intermittently unavailable on Saturday, March 24th, from 16:00 until 20:00 UTC.
I'd like to open up my test scripts for l10n to a wider audience and put them on the public CVS. It's a bunch of python scripts and packages (or one) together with web content, intended to gather information from the l10n repository in an automated way. I was thinking of mozilla/testing/l10n, which would contain setup.py and lib, scripts and web subdirectories for now.
I tend to agree that somewhere in mozilla/testing is the right home for these scripts. I'm not sure about .../l10n, though. I'll chat with the build folks about it and get back to you.
Could I get feedback on this soon? I'd rather focus on Firefox2.0 than cvs directory names.
Axel, in #build, we came up with the suggested directory: mozilla/testing/tests/l10n How does that sound to you?
Works for me. I would expect 'tests' to be tests instead of testing tools, but that's not what's in that dir, so mozilla/testing/tests/l10n it is. I'll create that tomorrow.
Hmmm. I think this could also live in l10n/testing/..., but having it live in mozilla/testing/... is ok since more people will look at it there . . . As far as whether this is a test - it is a script that is run to report information about the codebase. I think that qualifies as a test.
Status: NEW → RESOLVED
Last Resolved: 12 years ago
Resolution: --- → FIXED
Make the sub-bugs for test/l10n a little more discoverable by adding them to the blocked bugs.
Component: Testing → Infrastructure
Product: Core → Mozilla Localizations
QA Contact: testing → infrastructure
Version: Trunk → unspecified
You need to log in before you can comment on or make changes to this bug.