AMO/SigningService: Difference between revisions

AMO/SigningService (view source)

168 bytes removed , 19 September 2014

m

Confirmed users, Bureaucrats and Sysops emeriti

1,737

edits

@@ Line 67: / Line 67: @@
 |}
-* Modifying the Validator to warn about pre-existing signatures which will be clobbered
+This will implement the initial AMO support, signing apps after being approved by reviewers.  This includes a management command to sign individual add-ons but not one to sign all existing add-ons.  It's not clear if we'll want to bootstrap with a script like that, but it will be easy enough to write later if we do.
-* Modifying the Reviewer Tools to send add-on data to Trunion and using the returned data to save a signed add-on to disk (<span style="color:red; font-weight:bold">API to Trunion needs definition</span>)
-* Modifying AMO to add a signing script which will sign the latest versions of existing add-ons to bootstrap the system
-* Modifying MDN by adding any necessary documentation about this project
 Open Bugs: