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:
Before going further, there's one helpful hint we can offer: if the
only change your extension requires is a bump to the |maxVersion|
field in its install manifest, and you host your extension at
addons.mozilla.org <https://addons.mozilla.org>, you don't actually
need to upload a new version of your extension! Simply use the
Developer Control Panel at AMO to adjust the |maxVersion|. You can
avoid having to have your extension re-reviewed this way.
But the text in Install Manifests - MDC
<http://developer.mozilla.org/en/docs/install.rdf#targetApplication>
isn't updated.
Does this also mean that for those extensions the entries em:minVersion
and em:maxVersion in install.rdf become obsolete?
Maybe someone with enough authority and knowledge of the matter can
change this text, so that it states that for extensions for applications
based on Gecko 1.9 and hosted on AMO, it is enough to specify the right
version on AMO.
Thank you,
Onno
_______________________________________________
Project_owners mailing list
[email protected]
https://www.mozdev.org/mailman/listinfo/project_owners
