CrashKill/Firefox4: Difference between revisions

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

@@ 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 use the keywords (reproducible, needs-info, testcase-wanted) to provide more detail on what is needed to move forward with the bug.
+* Ensure that new crash regressions are logged.
-* We will make sure the module owner is cc'd on the bug so they can be assigned appropriately.
+* Monitoring crash trends and regular reports on general stability to the team.
-* The Crashkill team will meet weekly to triage bugs, discuss trends and monitor progress.
+* Consistent use of keywords (reproducible, needs-info, testcase-wanted) to provide more detail on what is needed to move forward with the bug.
-* We will be maintaining this list through the end of the release cycle.
+* Ensure module owners are cc'd on the bugs so they can be assigned appropriately.
-* Old Crashkill notes and info can be found at https://wiki.mozilla.org/CrashKill.
-==Bug Lists==
+==Latest Stability Data (04/18/11)==
-The base search query here is keyword=topcrash and blocking 2.0=beta, final.
+* 4.0.1 is almost ready to go out.
-* [http://bit.ly/bBI9jk All top crashers]
+==Status==
-* [http://bit.ly/dhOL4Z Top crashers - nominated]
+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.
-* Top crashers - reproducible
-* Top crashers - needs info
-* Top crashers - fixed
-* [http://bit.ly/ak25bO Unassigned (nobody@mozilla.org, general@js.bugs)]
-* Fixed bugs
-==Next Actions==
+[https://crash-stats.mozilla.com/topcrasher/byversion/Firefox/4.0 Firefox 4 crashes in past 7 days]
-* Crashkill team meeting today to triage bugs and fill out the list of top 25 crashers.
+===Crashes addressed in 4.0.1===
-* 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==
+* [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://crash-stats.mozilla.com/products/Firefox
+===Top issues we are still trying to make progress on ===
+* [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)]
+* [https://bugzilla.mozilla.org/show_bug.cgi?id=637304 bug 637304 (#5 top browser crash for FF4)]
 ==Meeting Logistics==
 *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)
 *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
+*Backchannel on irc.mozilla.org is #crashkill
-==Meeting Notes==