533948 - Add SeaMonkey 2.0.1 explicitly in AMO

Status: VERIFIED FIXED

(addons.mozilla.org Graveyard :: Administration, defect, P3)

Description

[Patrick Brunschwig]

Given the API change from Thunderbird between SeaMonkey 2.0 and 2.0.1, I'd suggest to add SeaMonkey 2.0.1 explicitly as version in AMO. This allows add-ons that depend on the API change (like Enigmail and Lightning) to explicitly mark compatibility with 2.0.1 and later, but not with 2.0.

Comment 1

[Robert Kaiser]

What API has changed between 2.0 and 2.0.1? There was supposed to be ZERO API changes there and we were not informed of any.

I'm not convinced that we need that version in there or that it's a good idea, but in any case, this is an AMO bug and not a SeaMonkey one.

Comment 2

[Patrick Brunschwig]

These both landed which affected API changes after SM 2.0 was released:

http://hg.mozilla.org/releases/comm-1.9.1/rev/7b68edce5121 (bug 248681)
http://hg.mozilla.org/releases/comm-1.9.1/rev/d79070dab585 (bug 465618)

The first of these adjusted nsIMsgCompFields and is known to crash Thunderbird and SeaMonkey if Enigmail doesn't use the same API version. So SM 2.0 really has a different API than 2.0.1 (even if the changes are relatively small) ...

Comment 3

[Wil Clouser [:clouserw]]

-> fligtar for decision

Comment 4

[Robert Kaiser]

(In reply to comment #2)
> These both landed which affected API changes after SM 2.0 was released

All I can say is "ouch" :(

May really warrant having that available though, true.

Comment 5

[Justin Scott [:fligtar]]

added

Comment 6

[Stephen Donner [:stephend] Not actively reading bugmail]

Looks like we added 2.0.*: https://addons.mozilla.org/en-US/seamonkey/pages/appversions

Verified FIXED.