Comment 12 for bug 1494442

Maybe the errors that testers experience are representative of the errors that customers experience. But even if that's true now, it won't necessarily be true all the time. There might be common errors that disproportionately/only affect customers using a language, time zone, keyboard, carrier, scope, or local app that our testers seldom use. Or errors that occur with the update process itself for a particular stable update. With error reporting turned off for stable, you won't know when this happens.

So, maybe a follow-up to this change could be to alter apport on stable to record just error statistics, not crash files. Then you wouldn't get a slowdown from dumping each crash, but you'd still be able to see when stable had an error rate higher than development channels for a particular package. When that happened, you could selectively turn on full error reporting for just that package to see what was going on.