Confirmed users
1,798
edits
Firefox/Channels/Meetings/2012-05-15: Difference between revisions
→Overall concerns
| Line 50: | Line 50: | ||
* Lots of new signatures over the last 4-6 mos, nothing happening. | * Lots of new signatures over the last 4-6 mos, nothing happening. | ||
* Need a formal strategy to get some of these worked. | * Need a formal strategy to get some of these worked. | ||
* RelMan's recommendation would be: | |||
** Go through each top crasher, read through crash comments, pull new correlation reports, update its status, and provide any leads for QA | |||
** Ask the QA community to try to find STR for each top crasher, with rewards if found (t-shirt/bounty?) | |||
** Automatically track all reproducible top crashers found for a future release and drive them as if they're a new regression | |||
** Remaining top crasher bugs would then be blocked on a bug that would collect the necessary debug info to diagnose | |||
===Aurora=== | ===Aurora=== | ||
* [http://bit.ly/K2EmSe Crashes tracking Fx14] | * [http://bit.ly/K2EmSe Crashes tracking Fx14] | ||