Support testing of language packs for new locales

RESOLVED FIXED

Status

Mozilla Localizations
Other
RESOLVED FIXED
12 years ago
10 years ago

People

(Reporter: Pike, Unassigned)

Tracking

(Depends on: 1 bug)

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

12 years ago
One of the things that we currently don't do very good is expose new locales in the making to testers. One way to do that would be to put language packs up on AMO. In this case, like regular extensions, that is, whenever the localizer submits one into the review queue. I wouldn't necessarily want to restrict this to registered locales or locales in our CVS.

Does that sound like a good idea?

If so, I had a few further questions:

- anyone missing on CC on this bug? If so, fix it ;-)

- should we expose these in a separate category than the one where our own release packs are planned to show? See bug 245946.

- as those xpis are supposed to be way more agile than our regular langpacks, I guess we should add the build id to the version, something like 2.0.0.2pre2007022110 or so.

- should we mangle the extension ID to distinguish these from our official language packs? This could be interesting mostly when we start taking a particular locale in official releases, at which point we run into bug 334136 with a tad more momentum.
(Reporter)

Comment 1

11 years ago
Making the remora category and the security update actually block this.
Depends on: 245946, 334136
(Reporter)

Updated

11 years ago
Depends on: 383582
(Reporter)

Comment 2

10 years ago
FIXED, open issues with langpacks on AMO are in separate bugs.
Status: NEW → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.