Onno Ekker wrote: > Parkway Neil wrote: >>> I did change the maxVersion of my Thunderbird extension in place to >>> 3.0a1 and I noticed the compatibility range on AMO changed, but in >>> the extensions install.rdf it's still maxVersion 2.0.0.*. >>> >>> What's the point in changing this in-place if you still need a new >>> xpi with a new install.rdf? >>> >> >> I believe the idea is that during installation the Extension Manager >> looks for updates to see if the compatibility range has been changed. >> > Ah... I was looking at the wrong page... > In Updating your extension for Firefox 3 - MDC > <http://developer.mozilla.org/en/docs/Updating_extensions_for_Firefox_3#Step_1:_Update_the_install_manifest> > > it indeed says so: > I suppose this also holds for Thunderbird 3.0a1. But as of yesterday I am co-author of an extension that is still marked in install.rdf and on AMO as being compatible with Thunderbird 1.5 - 1.5.0.*. When I change this version inline to 1.5 - 3.0a1 all Thunderbird 2.0.0.* users will have a problem installing it, right? Wasn't there an issue with broken version ranges on AMO?
Onno _______________________________________________ Project_owners mailing list [email protected] https://www.mozdev.org/mailman/listinfo/project_owners
