addons-server: Internal Mozilla-signed add-ons are legacy but should not have compatibility restrictions
For the foreseeable future, AMO will be getting legacy submissions that are signed with the internal Mozilla certificate, which gives them the ability to be installed in Firefox 57 and above. We need to make an exception for these add-ons in our compatibility restrictions. Specifically:
- It should be possible to upload them without an admin override.
- They shouldn’t have strict compatibility and should appear as compatible in 57 and above.
- They should show the
Compatible with 57+tag. - They shouldn’t have lower ranking on search results.
For an example, see Firefox multi-account containers.
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Reactions: 1
- Comments: 33 (19 by maintainers)
Commits related to this issue
- Allow legacy, mozilla-signed add-ons to be submitted. Refs #6424, first part of allowing mozilla owned and signed legacy add-ons that are compatible with Firefox 57. — committed to mozilla/addons-server by EnTeQuAk 7 years ago
- Allow legacy, mozilla-signed add-ons to be submitted. (#6458) * Allow legacy, mozilla-signed add-ons to be submitted. Refs #6424, first part of allowing mozilla owned and signed legacy add-ons th... — committed to mozilla/addons-server by EnTeQuAk 7 years ago
- Show all versions for mozilla signed legacy extensions. Refs #6424 — committed to mozilla/addons-server by EnTeQuAk 7 years ago
@ValentinaPC only users with a
@mozilla.comemail can submit a Mozilla Signed Extension.