Firefox/Channels/Meetings/2012-05-15: Difference between revisions

← Older edit

Firefox/Channels/Meetings/2012-05-15 (view source)

Revision as of 17:41, 17 May 2012

2,295 bytes added , 17 May 2012

→‎Previous Actions

Lsblakk

Confirmed users

4,467

edits

@@ Line 26: / Line 26: @@
 * <strike>Alex to follow up on the Hotmail regression {{bug|736731}}</strike>
 * <strike>Alex to speak with Kev re: Silverlight crash {{bug|753248}}</strike>
-* Michelle to file bug on Input for rapid betas build IDs {{bug|754050}}
+* <strike>Michelle to file bug on Input for rapid betas build IDs {{bug|754050}}</strike>
 == Schedule Update ==
@@ Line 37: / Line 37: @@
 * FF13 beta 4 will go-to-build today (5/15). We've asked engineering to continue working on [https://bugzilla.mozilla.org/buglist.cgi?field0-3-0=cf_status_firefox13;type0-1-0=notequals;value0-4-0=verified;field0-1-0=cf_status_firefox13;field0-0-0=cf_tracking_firefox13;type0-4-0=notequals;value0-3-0=unaffected;query_format=advanced;value0-2-0=fixed;value0-1-0=wontfix;type0-3-0=notequals;field0-2-0=cf_status_firefox13;field0-4-0=cf_status_firefox13;type0-0-0=equals;value0-0-0=%2B;type0-2-0=notequals;list_id=3088165 tracked bugs], looking for the lowest risk mitigating fix for remaining tracked bugs
-* The next 3.6 EOL checkpoint is 5/28 when we push out the last round of MUs
+* The next 3.6 EOL checkpoint is 5/28 when we push out the last round of MUs (one more auto-update round still to follow)
 ==Add-ons==
@@ Line 50: / Line 50: @@
 * Lots of new signatures over the last 4-6 mos, nothing happening.
 * Need a formal strategy to get some of these worked.
+* RelMan's recommendation would be:
+** Go through each top crasher, read through crash comments, pull new correlation reports, update its status, and provide any leads for QA
+** Ask the QA community to try to find STR for each top crasher, with rewards if found (t-shirt/bounty?)
+** Automatically track all reproducible top crashers found for a future release and drive them as if they're a new regression
+** Remaining top crasher bugs would then be blocked on a bug that would collect the necessary debug info to diagnose
 ===Aurora===
 * [http://bit.ly/K2EmSe Crashes tracking  Fx14]
 * A couple of problems with AMD graphics cards {{bug|714320}} and {{bug|700288}} that we haven't been able to fix.
 * {{bug|736695}} - nsGenericElement::UnbindFromTree , when I open Customize Toolbar with Video DownloadHelper 4.9.8 installed. A problem for a while.
+* {{bug|753248}} - startup crash - silverlight issue on Mac 10.7.
 ===Beta===
-<br>
+* {{bug|704125}} - spike in crashes for banco de brazil.
 ===Release===
 * In preparation for 10.8, we're now watching for [https://crash-analysis.mozilla.com/chofmann/20120514/top-mac-crashes-all.txt Mountain Lion top crashers]
@@ Line 68: / Line 77: @@
 <br>
 ===Beta===
-<br>
+[http://bit.ly/IhfxAz QAWANTED Bugs]
+* Nothing in particular to discuss (ie. QA is not currently blocked on testing anything)
 == RelEng ==
 * win8
@@ Line 75: / Line 86: @@
 == Marketing/Communications ==
+* Handing off Desktop  to Laura Forrest, with official hand-off date being 6/18.
+** Unclear how this affects Aurora & Beta ownership
+** Laura M and Grace will continue to own Desktop through Fx 13 launch, with Laura F taking on more and more as the weeks go by.
+*** questions: send to pmm@mozilla.com
+* Haven't gotten a naming agreement yet for new betas. Will have for sure for Thursday.
 <br>
+== Support ==
+<br>
+Quick updates from Input: Looks like Netflix is broken in beta(?) [http://input.mozilla.org/en-US/?q=netflix&product=firefox&version=13.0&date_start=&date_end=] (Looks like it doesn't play in Win7, but it doesn't stop when you close tab in OSX -- this problem also happens in youtube in windows: [http://input.mozilla.org/en-US/?product=firefox&version=13.0&date_start=&date_end=&q=youtube]).  Firebug is broken in aurora [http://input.mozilla.org/en-US/?q=firebug&product=firefox&version=14.0a2&date_start=&date_end=].
 == Roundtable ==
 * Rapid Betas - any lingering questions?
+** (ashughes) - not a question, but I emailed around a proposal for QA automation:
+*** limit locales to en-US + 1 random per platform
+*** limit add-on pool to top-50
+*** use add-on bucketing of top-10 + 10 random
+*** should reduce execution time to ~4 hours
+*** Q) Is that still too long? Is there too much risk involved in those reductions?
 * Marcia plans to have a full QA test plan for Mountain Lion soon
 * We're pursuing multiple avenues for how to handle the lack of Russian users on Beta, and specifically our difficulty with reproducing Yandex Toolbar issues
@@ Line 83: / Line 110: @@
 ** We're also trying to get a Russian QA contact to help reproduce crashes, and considering sending out a CTA for Russian QA testers
 * Investigating decoupling Merge from Release Day: https://etherpad.mozilla.org/merge-day
+* What can we do about these [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=722312%2C700288%2C714320%2C745515%2C;list_id=3089183 Radeon top crashers]?
-* [https://bugzilla.mozilla.org/buglist.cgi?type0-1-0=nowordssubstr;list_id=3088568;field0-1-0=cf_tracking_firefox14;field0-0-0=cf_blocking_fennec10;query_format=advanced;value0-1-0=fixed%20verified;type0-0-0=equals;value0-0-0=betaN%2B betaN+] blocking bugs for FN14b2
+* [https://bugzilla.mozilla.org/buglist.cgi?type0-1-0=nowordssubstr;list_id=3089612;field0-1-0=cf_status_firefox14;field0-0-0=cf_blocking_fennec10;query_format=advanced;value0-1-0=fixed%20verified;type0-0-0=equals;value0-0-0=betaN%2B betaN+] blocking bugs for FN14b2
+* Pulling release from Android store
 == Actions ==