Since bug 271812 is fixed the DOM Inspector is now available on AMO. The only thing which should be done now is to sign this extension. Currently there is shown an unknown author during the installation. Shawn, I think that your name should be listed here?
I think it should say mozilla.org or something. Do we have a certificate in which to do that?
Dunno, I presume we have some sort of code-signing cert for Windows installers at least, but it might not be the right flavour. Best to mail someone in build-land.
Basil, Kev: Is this related to bug#401284 and therefore something you should take? Or am I missing something?
(In reply to comment #3) > Basil, Kev: Is this related to bug#401284 and therefore something you should > take? Or am I missing something? I can't see that bug to comment for sure, but I suspect not (unless it's something like AMO should automatically sign add-ons). I guess what should be addressed by build is if we have a cert to sign add-ons or not.
Shawn; bug#401284 is about that cert, so there's nothing left for Release to do here. Reassigning this bug to addons.m.o/policy so that Basil or Kev can take it from here.
Component: Release Engineering → Policy
Product: mozilla.org → addons.mozilla.org
QA Contact: build → policy
Version: other → unspecified
Shawn, do consider DOM-I to be "owned" by Mozilla? If so, John, can we use the mentioned cert to sign this addon?
It's a mozilla.org project, so yes.
Basil: we've never used the certificate mentioned in bug#401284, so dont know if it can be used to sign addons like this. Maybe Justin and/or the certificate vendor can help?
Component: Policy → DOM Inspector
Product: addons.mozilla.org → Other Applications
QA Contact: policy → dom-inspector
This isn't worth the hassle.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.