MozillaWiki

CrashKill/Firefox4: Difference between revisions

< CrashKill
No edit summary
 
(62 intermediate revisions by 2 users not shown)
Line 1: Line 1:
==General Agenda==
==General Mandate==


* To resurrect the Crashkill effort targeted specifically at the 2.0 release.  
* Monitor and track the stability metrics specifically focused on the Firefox 4 release.
* We would like to focus the developers' efforts on addressing a top 25-30 list of the most serious crashers.  
* Focus people's attention on addressing the most serious crashers particularly regressions.
* We will also be monitoring crash trends and reporting on general stability.
* Ensure that new crash regressions are logged.
* We will use the keywords (reproducible, needs-info, testcase-wanted) to provide more detail on what is needed to move forward with the bug.
* Monitoring crash trends and regular reports on general stability to the team.
* We will make sure the module owner is cc'd on the bug so they can be assigned appropriately.
* Consistent use of keywords (reproducible, needs-info, testcase-wanted) to provide more detail on what is needed to move forward with the bug.
* The Crashkill team will meet weekly to triage bugs, discuss trends and monitor progress.
* Ensure module owners are cc'd on the bugs so they can be assigned appropriately.
* 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==
==Latest Stability Data (04/18/11)==


The number of crashing bugs on the trunk has increased dramatically over the past 10 days.  
* 4.0.1 is almost ready to go out.  


The following crash reports demonstrate this trend...
==Status==
*[http://people.mozilla.com/~chofmann/crash-stats/20101017/top-4.0b8pre.html Crash stats from 2010-10-17]
Most of the top crashes are compatibility or malware related. Working on outreach and other projects to tackle some of the top issues. Some crashes will be addressed in 4.0.1.  
*[http://people.mozilla.com/~chofmann/crash-stats/20101010/top-4.0b8pre.html Crash stats from 2010-10-10]


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).
[https://crash-stats.mozilla.com/topcrasher/byversion/Firefox/4.0 Firefox 4 crashes in past 7 days]


*[http://bit.ly/bKE7nQ List of crash bugs we want to track and get resolved]
===Crashes addressed in 4.0.1===


There are another 15 bugs in the nominated state we should review as well.
* [https://bugzilla.mozilla.org/show_bug.cgi?id=601102 bug 601102]
* [https://bugzilla.mozilla.org/show_bug.cgi?id=637367 bug 637367]
* [https://bugzilla.mozilla.org/show_bug.cgi?id=640652 bug 640652]
* [https://bugzilla.mozilla.org/show_bug.cgi?id=639885 bug 639885]
* [https://bugzilla.mozilla.org/show_bug.cgi?id=640901 bug 640901]
* [https://bugzilla.mozilla.org/show_bug.cgi?id=643515 bug 643515 (dup of 640901)]
* [https://bugzilla.mozilla.org/show_bug.cgi?id=641057 bug 641057]
* [https://bugzilla.mozilla.org/show_bug.cgi?id=643746 bug 643746 (might be fixed by bug 601102]


*[http://bit.ly/c61Yme List of crashes nominated for 2.0]
===Top issues we are still trying to make progress on ===


==Bug Lists==
* [https://bugzilla.mozilla.org/show_bug.cgi?id=633445 bug 633445 (#1 top browser crash for FF4)]
 
* [https://bugzilla.mozilla.org/show_bug.cgi?id=615098 bug 615098 (#3 top browser crash for FF4)]
* Top crashes - (keyword=topcrash and blocking 2.0=beta, final)
* [https://bugzilla.mozilla.org/show_bug.cgi?id=637304 bug 637304 (#5 top browser crash for FF4)]
** [http://bit.ly/bBI9jk All top crashers]
** [http://bit.ly/dhOL4Z Top crashers - nominated]
** [http://bit.ly/di44gH Top crashers - reproducible]
** Top crashers - needs info
** [http://bit.ly/aIlAP8 Top crashers - regressions]
** [http://bit.ly/aR5i5F Top crashes - not modified since 2010-09-01]
** [http://bit.ly/du1lZm Top crashers - fixed] (so we can go back verify in the next beta).
** [http://bit.ly/ak25bO Unassigned (nobody@mozilla.org, general@js.bugs)]
 
* All crashes - (keyword=crash, topcrash and blocking 2.0=beta, final)
** [http://bit.ly/dxjuFe All crashes]
** [http://bit.ly/bk4Qml All crashes - fixed]
** [http://bit.ly/dk7Lki All crashes - not modified since 2010-09-01]
 
==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==
==Meeting Logistics==


*Dial-in for the meeting is x290
*Dial-in for the meeting is x290
*The Meeting is now every! Tuesday at 12:30AM till 1PM Pacific
*The Meeting is now every Monday at 10:30AM till 11:00am Pacific
*650-903-0800 or 650-215-1282 x92 Conf# 290 (US/INTL)
*650-903-0800 or 650-215-1282 x92 Conf# 290 (US/INTL)
*1-800-707-2533 (pin 369) Conf# 290 (US)
*1-800-707-2533 (pin 369) Conf# 290 (US)
*MV - Meet in Zombocom Conference Room on Floor 3.
*MV - Meet in Zombocom Conference Room on Floor 3.
*Backchannel on irc.mozilla.org is #planning
*Backchannel on irc.mozilla.org is #crashkill
 
==Meeting Notes==

Latest revision as of 17:53, 26 April 2011

General Mandate

  • Monitor and track the stability metrics specifically focused on the Firefox 4 release.
  • Focus people's attention on addressing the most serious crashers particularly regressions.
  • Ensure that new crash regressions are logged.
  • Monitoring crash trends and regular reports on general stability to the team.
  • Consistent use of keywords (reproducible, needs-info, testcase-wanted) to provide more detail on what is needed to move forward with the bug.
  • Ensure module owners are cc'd on the bugs so they can be assigned appropriately.

Latest Stability Data (04/18/11)

  • 4.0.1 is almost ready to go out.

Status

Most of the top crashes are compatibility or malware related. Working on outreach and other projects to tackle some of the top issues. Some crashes will be addressed in 4.0.1.

Firefox 4 crashes in past 7 days

Crashes addressed in 4.0.1

Top issues we are still trying to make progress on

Meeting Logistics

  • Dial-in for the meeting is x290
  • The Meeting is now every Monday at 10:30AM till 11:00am 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 #crashkill
Retrieved from "https://wiki.mozilla.org/index.php?title=CrashKill/Firefox4&oldid=302811"