if developers are working on an addon used in build or test automation, initially the onus will be on them to use the AMO signing api and pre-sign them before checking into gecko. Developers will need to be pointed to documentation for this.
ahal wrote great documentation here, thanks ahal! https://wiki.mozilla.org/EngineeringProductivity/HowTo/SignExtensions
Assignee: nobody → ahalberstadt
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → FIXED
Component: General Automation → General
Product: Release Engineering → Release Engineering
You need to log in before you can comment on or make changes to this bug.