Open Bug 639458 Opened 13 years ago Updated 2 years ago

Translation xpi's compatibility requirements too tight for release (4.0rc1)

Categories

(Firefox Build System :: General, defect)

Product:
Firefox Build System
Component:
General
Version:
Other Branch
Platform:
All
Linux
Type:
defect

Tracking

(Not tracked)

People

(Reporter: chrisccoulson, Unassigned)

Details

I haven't checked all translation xpi's on ftp://ftp.mozilla.org/pub/firefox/nightly/4.0rc1-candidates/build1/linux-x86_64/xpi/ yet, but I downloaded en-GB.xpi and checked its install.rdf, and it has minVersion=maxVersion=4.0.

To me, this implies that there are string changes expected in point releases.

If this isn't the case, could we please widen this for the stable releases? The 3.6 release xpi's all seem to have minVersion=3.6b2,maxVersion=3.6.* in their install.rdf instead.

Having the compatibility requirements set so tight is going to be a bit of a headache for distributors. In Ubuntu, we distribute these xpi's in our language packs, and coordinating language pack respins for every Firefox security update is not going to be much fun :)
Right, we need the same thing as we did in bug 531059 for 3.6.x
... or should we do that after branching on 2.0 only?
2.0 has branched already hasn't it? http://hg.mozilla.org/releases/mozilla-2.0/. I think that's where the RC1 builds are coming from.
The builds are coming from there, but the repos are not in action yet, they're solely in hands of releng so far.
Product: Core → Firefox Build System
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.