CrashKill/Firefox4

General Agenda

To resurrect the Crashkill effort targeted specifically at the 2.0 release.
We would like to focus the developers' efforts on addressing a top 25-30 list of the most serious crashers.
We will also be monitoring crash trends and reporting on general stability.
We will use the keywords (reproducible, needs-info, testcase-wanted) to provide more detail on what is needed to move forward with the bug.
We will make sure the module owner is cc'd on the bug so they can be assigned appropriately.
The Crashkill team will meet weekly to triage bugs, discuss trends and monitor progress.
We will be maintaining this list through the end of the release cycle.
Old Crashkill notes and info can be found at https://wiki.mozilla.org/CrashKill.

The number of crashing bugs on the trunk has increased dramatically over the past 10 days.

The following crash reports demonstrate this trend...

There are a number of open bugs we would like to track between now and the beta to ensure they get resolved (blocking2.0 changed since 2010-10-13).

There are a number of bugs in nominated state we should review as well. These have been added since 2010-10-13.

Crashkill team meeting today to triage bugs and fill out the list of top 25 crashers.
Confirm that the list consists of bugs that we can move forward and work on.
Get the nominated items through the queue.
Make sure top list bugs are assigned to developers.