Closed Bug 698358 Opened 13 years ago Closed 13 years ago

Add support for new strictCompatibility option in install.rdf

Categories

(addons.mozilla.org Graveyard :: API, defect, P2)

defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: Unfocused, Assigned: robhudson)

References

Details

Bug 693897 will allow addons to opt-in to strict-compatibility checking (ie, the old-style, where addons aren't compatible by default). Seems beneficial for the AMO side to support this too - namely in the API responses, and update pings (see bug 698355). And I guess in determining compatibility when showing the addon on addons.mozilla.org.

The option in install.rdf is a boolean, defaulting to "false" when the option is missing (this will be the most common case). It will appear in install.rdf as:

<strictCompatibility>true</strictCompatibility>
Er, clarification: It will appear in install.rdf as:

<em:strictCompatibility>true</em:strictCompatibility>
Assignee: nobody → chudson
Target Milestone: --- → 6.3.1
Priority: -- → P2
Target Milestone: 6.3.1 → 6.3.2
https://github.com/mozilla/zamboni/commit/22ae51f
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.