AMO/history
This page keeps the history of AMO: what we've been working on, when, events, pushes... Glossary:
- -dev: the dev server
- stage: the stage server
- prod: the production server
2015-04-25 (saturday crisis)
It was reported that the signing of the 400 add-ons caused crashes of Firefox versions 28 and below (and derivatives) when doing a version update check. We thus decided to revert the signing of those add-ons until we find a fix for that issue.
- 1158467 Signed extensions on AMO have invalid signatures
- create PR #526 to revert auto signing
- cherry-pick and tag 2015.04.25
- 0882d3a Revert auto signing (bug 1158467)
2015-04-24
The auto/bulk signing script is finally ready to deploy to production after some extensive testing on -dev and stage. The signatures are done correctly, on the published add-ons, with the correct certificate, and the emails are sent to the add-on owners.
We thus decided to push to production, and run the script on a chosen list of 400 add-ons.
- 1070227 Write a script to sign all existing add-ons (send email to addon owners)
- create PR #525
- cherry-pick and tag 2015.04.24
- a9638bb Send an email to addon owners after their addon got auto signed (bug 1070227)
2015-04-23
Continue working on the unlisted add-ons feature. The tag 2015.04.22 that was planned to be pushed to production was not, because we decided we needed to send mails to the add-on owners.
/!\ cannot be cherry-picked on the tag in production, as it touches codes related to unlisted addons, which isn't in production yet.
2015-04-22
Continue working on the unlisted add-ons feature. Main change: there's now a waffle flag for the automatic validation feature, in prevision for the push to production of the unlisted add-ons feature. We're not sure the automatic validation will be ready, so it's now disabled by default until we turn the flag on.
It was finally decided that we should only auto/bulk sign add-ons that are compatible with Firefox, and only if
- they are default to compatible and Firefox version >= 4
- they aren't default to compatible (binary components or strict compatibility) and Firefox version >= 37
We tagged for a push to stage, and planned a push to production on thursday 2015-04-23.
- reviewed #515
- 1148447 Adjust flow to be steps 1 -> 2 -> 3ish -> 7
- update PR #505 following reviews
- create bug 1157215 add a waffle flag for the automatic validation
- create PR #521
- committed 343dfec Add lib.crypto.tasks to the CELERY_IMPORTS: celery workers on -dev and stage were failing because this was missing
- create bug 1157444 Only bulk sign versions that are compatible with recent versions of Firefox
- create PR #523
- cherry-pick and tag 2015.04.22
- sign_addons bulk signing script tested on:
- flash-video-downloader: correctly signed all versions above ff10 that were reviewed
- lookout: correctly didn't sign any version, it's compatible thunderbird and seamonkey only
