Firefox/Channels/Meetings/2012-04-19
From MozillaWiki
Channel Meeting Details
- Tuesdays and Thursday - 2:00pm PDT, 21:00 UTC
- Mountain View Offices: Warp Core Conference Room
- irc.mozilla.org #planning for backchannel
Video/Teleconference Details - NEW
- 650-903-0800 or 650-215-1282 x92 Conf# 95312 (US/INTL)
- 1-800-707-2533 (pin 369) Conf# 95312 (US)
- Vidyo Room: Warp Core
- Vidyo Guest URL
REMEMBER
These notes are read by people who weren't able to attend the meeting. Please make sure to include links and context so they can be understood.
Contents
Previous Actions
Schedule Update (stay up to date)
- Firefox 12 was signed off yesterday (4/18)
- 3.6.{28,27,26,25,13,24} should be receiving a major update prompt to FF11 with this billboard, remaining 3.6.{14-23} to be completed tomorrow
- FF12 beta 6 (desktop) is still expected to go out today, pending QA sign-off
- Desupport hotfix (bug 741004) is being tested end-to-end by QA currently, will hopefully go out this afternoon as well
- FF12 desktop and FF10.0.4 desktop/mobile go-to-build expected tomorrow at noon PT
- Release is scheduled for 4/24
- Next 3.6 MUs will be after FF12 fully unthrottled, and will point to this billboard (but on production)
Add-ons
Stability
- no crash rates due to metrics data center move.
- explosive crash reports also broken due to above.
Aurora
- Tracking 13 crashes
- bug 719117 - did they change some code in 13? Maybe the signature is just different but doesn't mean more crashes.
- bug 729507 - correlation to Yandex bar?
- bug 743499 - ESR? Patch that got reviewed yesterday. Affects all versions.
- bug 744727 - crash on mouse move - has landed on 12. Still open.
- bug 745453 - Norton Confidential 2012 - fixed in FF12b6. Still open for verification.
- bug 746036 - Needs investigation
- bug 725503 - 3rd party issue FF12 also
- bug 744992 - web.de - 3rd party issue FF12 also
Beta
- Don't see anything that we didn't know about already.
Release
QA
Aurora
Beta
RelEng
Marketing/Communications
Roundtable
- Cheng filed bug 747073 – Adobe Reader (10.1.3) doesn't work with Firefox 11 (OSX)
- Appears to be a problem with Adobe's software
- A couple of security bugs on the approval-mozilla-beta list to talk about
- Proposal to set a 'bounty' (read: cool custom swag) on finding verifiable topcrasher STR (more to be added to list, and third-party crashes not eligible). Once STR are verified, we can track them for a specific release.
Actions