remove throttle rules for Thunderbird and SeaMonkey future versions
Categories
(Socorro :: Antenna, task, P2)
Tracking
(Not tracked)
People
(Reporter: willkg, Assigned: willkg)
References
Details
Attachments
(1 file)
In bug #1604848 and bug #1619101, we added throttle rules to reject incoming crash reports for future versions of Thunderbird and SeaMonkey.
We're abandoning that plan and working with Thunderbird and SeaMonkey projects on a new one that has a different timeline and steps. That'll get figured out over the next week or two.
We no longer want the throttle rules. This bug covers removing them.
Assignee | ||
Comment 1•3 years ago
|
||
I'll do this on Monday.
Comment 2•3 years ago
•
|
||
working with Thunderbird and SeaMonkey projects on a new one that has a different timeline and steps. That'll get figured out over the next week or two.
Will, is the plan impacted by the cost of disk required for crash reports? If disk space does have a significant impact then we might consider the idea of keeping just 50% of release channel crash reports (I no longer remember the exact terminology of how that is accomplished in the collector), because I know that "release" channel currently has a high crash rate. That said, I haven't totally thought through the impact of doing this.
Assignee | ||
Comment 3•3 years ago
|
||
Wayne: I'm not sure what that has to do with removing the throttle rules. Maybe you meant to comment in bug #1608971?
Comment 4•3 years ago
|
||
My comment is speculative in that it might impact your plans hinted at in comment 0. But no one on the Thunderbird team I have spoken to knows what is meant by "We're abandoning that plan and working with Thunderbird and SeaMonkey projects on a new one that has a different timeline and steps. That'll get figured out over the next week or two."
That said, someone on the team was going to reach out to you to come to some arrangement for continuing to accept crashes for Thunderbird. So I guess the question is, who on the Thunderbird are you working with?
Assignee | ||
Comment 5•3 years ago
|
||
Assignee | ||
Comment 6•3 years ago
|
||
Assignee | ||
Comment 7•3 years ago
|
||
I pushed this change to prod with bug #1625479. Marking as FIXED.
Description
•