AMO/SigningService: Difference between revisions

m (→‎Roadmap: minor typo fix)
(→‎Schedule of Signing Rollout: schedule crrection)
 
(12 intermediate revisions by 2 users not shown)
Line 2: Line 2:


Hi.  This project is the AMO piece of the larger [https://docs.google.com/a/mozilla.com/document/d/1KhpDteoHFmVRkzlrT8v0N3F-KrPxLoZFM3mWmEmOses/edit Add-on Signature System].  Please read that document so the rest of this wiki page makes sense.
Hi.  This project is the AMO piece of the larger [https://docs.google.com/a/mozilla.com/document/d/1KhpDteoHFmVRkzlrT8v0N3F-KrPxLoZFM3mWmEmOses/edit Add-on Signature System].  Please read that document so the rest of this wiki page makes sense.
== Meetings ==
*the Add-On Signing Team meets Fridays at 16:00 UTC (9am Pacific). Meeting minutes are archived [https://wiki.mozilla.org/AMO/SigningService/Meetings here]
== Signing Architecture ==


We will need to modify several pieces of AMO and its libraries in order to accommodate this new system.  Those changes are roughly laid out below and divided up into phases.  See the diagram below (which compares to Marketplace for a reference) for a high level view:
We will need to modify several pieces of AMO and its libraries in order to accommodate this new system.  Those changes are roughly laid out below and divided up into phases.  See the diagram below (which compares to Marketplace for a reference) for a high level view:
Line 22: Line 27:


=== Schedule of Signing Rollout ===
=== Schedule of Signing Rollout ===
(updated May 28, 2015)
(updated September 15, 2015)


*May 22: Go live date for updated developer policy (MDN)
* Firefox 40-42: Firefox warns about signatures but doesn't enforce them.
*May 28: sign all AMO add-ons
* Firefox 43: Firefox will have a preference that allows signature enforcement to be disabled (xpinstall.signatures.required in about:config).
*June 1: All new AMO submissions get signed automatically
* Firefox 44: Release and Beta versions of Firefox will not allow unsigned extensions to be installed, with no override.
*June 1: Submission opens for non-AMO addons
*June 2: Firefox 38.0.5
*June 4: validator online + AMO push
*June 30: 40 Beta / 41 Aurora (signing enforced in 40 with pref to disable)
*Aug 11: 40 Release / 41 Beta (signing enforced with no pref except for ESR)
*Oct 6: 41 Release


=== Phase 1: Signing with Trunion===
=== Phase 1: Signing with Trunion===
Line 73: Line 72:
{
{
     "blocks": "1070152",
     "blocks": "1070152",
     "include_fields": "id, priority, status, summary"
     "include_fields": "id, priority, status, summary",
    "status": ["UNCONFIRMED", "ASSIGNED", "NEW", "REOPENED"]
}
}
</bugzilla>
</bugzilla>
Line 87: Line 87:


Open Questions:
Open Questions:
* How do we push updates to all existing add-ons after they are signed?  Updating to a new version number may be necessary.
* How do we push updates to all existing add-ons after they are signed?  Updating to a new version number may be necessary. ([andym] is this still a valid question, or has it been answered?)
 
Tracking bug: {{Bugzilla|1070153}}


Open Bugs:
Open Bugs:
Line 93: Line 95:
{
{
     "blocks": "1070153",
     "blocks": "1070153",
     "include_fields": "id, priority, status, summary"
     "include_fields": "id, priority, status, summary",
    "status": ["UNCONFIRMED", "ASSIGNED", "NEW", "REOPENED"]
}
}
</bugzilla>
</bugzilla>
Line 121: Line 124:
{
{
     "blocks": "1070154",
     "blocks": "1070154",
     "include_fields": "id, priority, status, resolution, summary"
     "include_fields": "id, priority, status, resolution, summary",
    "status": ["UNCONFIRMED", "ASSIGNED", "NEW", "REOPENED"]
}
}
</bugzilla>
</bugzilla>
Line 140: Line 144:
{
{
     "blocks": "1122114",
     "blocks": "1122114",
     "include_fields": "id, priority, status, summary"
     "include_fields": "id, priority, status, summary",
    "status": ["UNCONFIRMED", "ASSIGNED", "NEW", "REOPENED"]
}
}
</bugzilla>
</bugzilla>
Line 156: Line 161:
{
{
     "blocks": "1130124",
     "blocks": "1130124",
     "include_fields": "id, priority, status, summary"
     "include_fields": "id, priority, status, summary",
    "status": ["UNCONFIRMED", "ASSIGNED", "NEW", "REOPENED"]
}
}
</bugzilla>
</bugzilla>
Confirmed users
613

edits