Closed Bug 808426 Opened 7 years ago Closed 7 years ago

Bump extension compatibilities in preparation for SM 2.15 [chatzilla, dom-inspector, venkman]

Categories

(SeaMonkey :: Release Engineering, defect)

SeaMonkey 2.13 Branch
defect
Not set

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: InvisibleSmiley, Unassigned)

References

Details

For users that have compatible-by-default disabled (extensions.strictCompatibility = true), the extensions SM comes bundles with (CZ, DOMI and Venkman) get disabled automatically with SM 2.15a2 (currently on Aurora) or later. To work around this, we need to bump the compatibilities in the respective extensions' install.rdf files and update the revisions to fetch in client.py. The current SM value is 2.15a1 (used-to-be trunk) across the board. [Toolkit/Firefox values have partly been bumped meanwhile but we should just update all to the equivalent values like we used to do in the past.]

I feel having a single bug for this on the SM side of Bugzilla is better to track all this so nothing gets lost. Additionally, by setting the dependency on SM2.13, we'll hopefully remember to do the bumps in time in the future, too (e.g. in preparation for SM 2.16 shortly after releasing SM 2.14).

Previous bumps:
http://hg.mozilla.org/chatzilla/rev/9b4c50d79971 rs=Silver
http://hg.mozilla.org/dom-inspector/rev/f66a82354858 rs=sdwilsh 
http://hg.mozilla.org/venkman/rev/621c9868129f rs=gijskruitbosch

[Tagging and client.py updating were also done but I didn't track these down.]

I'll do the bumps and then unassign myself from this (hand-over to releng for the rest).
Bumped to 2.16a1 (19.0a1):
http://hg.mozilla.org/chatzilla/rev/1e6fa0b11c8f
http://hg.mozilla.org/dom-inspector/rev/d3a6dc0e1456
http://hg.mozilla.org/venkman/rev/55638304f158

ewong/Callek, please take over for tagging and client.py updating.
Assignee: jh → nobody
Status: ASSIGNED → NEW
Callek updated client.py:
http://hg.mozilla.org/releases/comm-beta/rev/c10fecfb9113
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.