On Sat, Feb 27, 2016 at 4:33 AM, Philip Chee <philip.c...@gmail.com> wrote:
> On 26/02/2016 22:45, Andrew Halberstadt wrote: > > To date, our continuous integration has been setting > > 'xpinstall.signatures.required=false' to bypass addon signing. But > > soon, this pref will become obsolete and Firefox will enforce signing > > no matter what. > > > > In preparation, we will begin signing extensions that are used in > > our test automation. If you maintain one of these addons, it means > > you will be required to re-sign it everytime a change is made. For > > more information on what this means, how to sign addons or how to > > bypass signing completely, see the following document: > > https://wiki.mozilla.org/EngineeringProductivity/HowTo/SignExtensions > > > > Let me know if you have any questions or concerns, Andrew > > We were promised that trunk and aurora builds would not enforce addon > signing when xpinstall.signatures.required=false. I did not see any > discussion about rescinding this commitment. > We also run automation on release-channel builds to test the bits we ship... > Phil > > -- > Philip Chee <phi...@aleytys.pc.my>, <philip.c...@gmail.com> > http://flashblock.mozdev.org/ http://xsidebar.mozdev.org > Guard us from the she-wolf and the wolf, and guard us from the thief, > oh Night, and so be good for us to pass. > _______________________________________________ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
