Confirmed users, Bureaucrats and Sysops emeriti
812
edits
Partnering/Repacks/Policy and Process: Difference between revisions
Partnering/Repacks/Policy and Process (view source)
Revision as of 18:30, 31 March 2015
, 31 March 2015clarify signing requirements for add-ons.
(clarify signing requirements for add-ons.) |
|||
| Line 38: | Line 38: | ||
''Effective as of Firefox 39'' | ''Effective as of Firefox 39'' | ||
All bundled add-ons included with a custom distribution must be signed in accordance with Mozilla's add-on signing policy. This will require that all bundled add-ons have passed full review | All bundled add-ons to be included with a custom distribution must already be signed in accordance with Mozilla's add-on signing policy. This will require that all bundled add-ons have passed full review through the AMO review process, whether that add-on is or is not distributed on AMO itself. | ||
The process for submitting add-ons that are not to be hosted on AMO will be announced in the near future, and should be live in May 2015. If an add-on is already hosted on AMO at that time, signing will happen automatically. Distribution partners will have priority for reviews, please contact Partner Support for more details. | |||
== Revenue-impacting Changes == | == Revenue-impacting Changes == | ||