Update maxVersions of applications for latest version bumps

[whimboo]

Yesterday the bump to 14.0a1 happened for Firefox. Similar bumps happen for other applications. We should get those in before releasing 3.2.2.

[whimboo]

This I can do at the same time as for the version bump to 3.2.2. Also we want to introduce the History.md file which will include all the changes for a given release.

[tonymec]

On 14/03/12 11:59, Henrik Skupin wrote:

Yesterday the bump to 14.0a1 happened for Firefox. Similar bumps happen for other applications. We should get those in before releasing 3.2.2.

Hm, yes. I'm not sure how the "default to compatible" feature applies to
NTT (there are binary components, but are they accessed by XPCOM?).

A few minutes ago I downloaded (and installed) what seems to be the last
SeaMonkey 2.10a1 trunk hourly: “Mozilla/5.0 (X11; Linux x86_64; rv:14.0)
Gecko/20120313 Firefox/14.0a1 SeaMonkey/2.10a1” ID:20120313221255

I see that since then, the first 2.11a1 nightly has been built. Probably
none of its langpacks yet but that is less important.

I suppose we could bump the maxVersion to Fx/Tb 14.* and Sm 2.11.*
unless AMO gives red cards to such "high" versions.

Best regards,

Tony.

The income tax has made more liars out of the American people than golf
has. Even when you make a tax form out on the level, you don't know
when it's through if you are a crook or a martyr.
-- Will Rogers

[whimboo]

Thanks for checking this Tony. Yes, we will have to bump the maxVersions given that we have a binary extension. It's important at least in those cases when users do not have an internet connection and trying to install the extension. Otherwise I will have to bump the maxVersion on AMO directly and an installation will fetch this value. Lets wait for todays builds, do the bump, and get a dev version up on AMO today.

[xabolcs]

tonymec wrote:

Hm, yes. I'm not sure how the "default to compatible" feature applies to NTT (there are binary components, but are they accessed by XPCOM?).

Currently NTT defines binary components in chrome.manifest so won't be compatible by default - only with these version bumps.

By the way NTT / Crash Me Now New uses ctypes to use those binary components.
I wondered to file and fix an issue about this ( let's name it: make NTT compatible by default).

OFFTOPIC:
Wondering about another enhanchment too: make NTT's crashme functionality gecko 1.9.x compatible :)

[tonymec]

On 14/03/12 15:15, Henrik Skupin wrote:

[...] Lets wait for todays builds, do the bump, and get a dev version up on AMO today.

Right.

Best regards,

Tony.

FIRST HEAD: All right! All right! We'll kill him first and then have tea and
biscuits.
"Monty Python and the Holy Grail" PYTHON (MONTY)
PICTURES LTD

[whimboo]

@xabolcs I don't really know if that qualifies an extension to become default by compatible. We still have binary components in it, using XPCOM or ctypes to call those shouldn't make a difference.

[xabolcs]

whimboo wrote:

@xabolcs I don't really know if that qualifies an extension to become default by compatible. We still have binary components in it, using XPCOM or ctypes to call those shouldn't make a difference.

Then try it! :)

1. get Firefox
2. get Crash Me Now! New
3. check it's install.rdf and chrome.manifest
4. install, restart
5. crash!

It works for me.

[whimboo]

Hm. Ok, can we get this moved to a new issue please? Looks like we should update to the new version then. Probably a good candidate for 3.2.3.