CrashKill/Firefox4: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 3: | Line 3: | ||
* To resurrect the Crashkill effort targeted specifically at the 2.0 release. | * 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 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 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. | * We will make sure the module owner is cc'd on the bug so they can be assigned appropriately. | ||
Revision as of 21:30, 18 October 2010
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.
Status
List of crash bugs we need to track and get resolved before the beta
Crash stats from 2010-10-17
Crash stats from 2010-10-10
Bug Lists
- Top crashes - (keyword=topcrash and blocking 2.0=beta, final)
- All top crashers
- Top crashers - nominated
- Top crashers - reproducible
- Top crashers - needs info
- Top crashers - regressions
- Top crashes - not modified since 2010-09-01
- Top crashers - fixed (so we can go back verify in the next beta).
- Unassigned (nobody@mozilla.org, general@js.bugs)
- All crashes - (keyword=crash, topcrash and blocking 2.0=beta, final)
Next Actions
- 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.
Analysis
http://crash-stats.mozilla.com/products/Firefox
Meeting Logistics
- Dial-in for the meeting is x290
- The Meeting is now every! Tuesday at 12:30AM till 1PM Pacific
- 650-903-0800 or 650-215-1282 x92 Conf# 290 (US/INTL)
- 1-800-707-2533 (pin 369) Conf# 290 (US)
- MV - Meet in Zombocom Conference Room on Floor 3.
- Backchannel on irc.mozilla.org is #planning