Bug 1624033 Comment 2 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

> 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 is required for crash reports?  If disk 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.
> 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.

Back to Bug 1624033 Comment 2