Closed Bug 1062386 Opened 7 years ago Closed 3 years ago

Report instances of damaged add-ons to AMO or through FHR

Categories

(Toolkit :: Add-ons Manager, defect, P3)

defect
Points:
2

Tracking

()

RESOLVED INACTIVE

People

(Reporter: mossop, Unassigned)

References

Details

We want to track when add-ons become damaged either by submitting information to AMO or through FHR.
Flags: firefox-backlog+
Flags: qe-verify?
Assignee: nobody → dtownsend
Points: --- → 2
Status: NEW → ASSIGNED
Iteration: --- → 40.1 - 13 Apr
Iteration: 40.1 - 13 Apr → 40.2 - 27 Apr
Assignee: dtownsend → nobody
Blocks: 1158200
No longer blocks: 1038071
Status: ASSIGNED → NEW
Iteration: 40.2 - 27 Apr → ---
Whiteboard: [fxsearch][searchhijacking]
Priority: -- → P5
Rank: 55
Whiteboard: [fxsearch][searchhijacking] → [hijacking][fxsearch]
Flags: needinfo?(dtownsend)
Priority: P5 → P3
Whiteboard: [hijacking][fxsearch]
See Also: → 1158214
Blocks: 1240191
Not sure what you needinfo'ed me for here, maybe because this bug is very poorly defined? I don't really know what we want and I don't really have any time to work on this. Unless you have a better idea than me we should just close this bug.
Flags: needinfo?(dtownsend) → needinfo?(amckay)
Sorry, I'm not sure either, but the main question we had was: what does damaged mean in this context? I think a report to FHR of the number of addons that:
* cannot be enabled because they do are not signed at all
* cannot be enabled because they do are signed incorrectly

Would be useful for us detecting problems in signing. If damage means something else, let us know. Wasn't implying that its for you to work on either.
Flags: needinfo?(amckay)
(In reply to Andy McKay [:andym] from comment #2)
> Sorry, I'm not sure either, but the main question we had was: what does
> damaged mean in this context? I think a report to FHR of the number of
> addons that:
> * cannot be enabled because they do are not signed at all
> * cannot be enabled because they do are signed incorrectly
> 
> Would be useful for us detecting problems in signing. If damage means
> something else, let us know. Wasn't implying that its for you to work on
> either.

I can't really remember, I'm guessing it was signed add-ons that later got detected as broken during the periodic check but it could be anything we want it to be at this point.
Per policy at https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Inactive_Bugs. If this bug is not an enhancement request or a bug not present in a supported release of Firefox, then it may be reopened.
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → INACTIVE
You need to log in before you can comment on or make changes to this bug.