CrashKill/Firefox4

From MozillaWiki
Jump to navigation Jump to search

General Agenda

  • To resurrect the Crashkill effort targeted specifically at the 2.0 release. We meet weekly to triage bugs and discuss issues.
  • We would like to focus the developers' efforts on addressing the most serious crashers particularly regressions.
  • 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.
  • Communicating status to the development team and others on the stability of the app.
  • Old Crashkill notes and info can be found at https://wiki.mozilla.org/CrashKill.

Status

(Updated Jan 19th, 2011)

We are now in the final stages of the release so monitoring for stability regressions is key. A few things we are tracking closely....

Crash Regressions From 3.6.13

  • 19 of the top 30 browser crashes are new in 3.6.13. Here is a complete list along with current status.

Plugin Crashes

Trunk Regressions

Bug Lists

A bunch of queries we like to refer to.

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

Meeting Notes