Firefox/Channels/Meetings/2013-01-31
From MozillaWiki
Channel Meeting Details
- Tuesdays at 10am Pacific, and Thursday at 2:00pm Pacific
- 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# 99951 (US/INTL)
- 1-800-707-2533 (pin 369) Conf# 99951 (US)
- Vidyo Room: Release Coordination
- Vidyo Guest URL
Previous meeting notes at: https://wiki.mozilla.org/Firefox/Channels/Meetings/2013-01-29
Contents
Previous Actions
Schedule Update
- FF19.0b4 (desktop) went out this afternoon
- FF19.0b4 (mobile) is going out tomorrow
- FF18.0.2 (bug 831626 only) will go to build tomorrow morning for desktop as long as the landing on Aurora looks good
- FF18.0.2 will be released once QA signs off and beta feedback is positive, likely early next week
RelEng
Add-ons
- [akeybl] CTP & enterprise (site whitelist)
- We can adapt Remote XUL Manager (https://addons.mozilla.org/addon/remote-xul-manager/)
- [akeybl] CTP & the latest Flash version (future)
- Looking into possible blocks: 835664, 835665, 835672, 835675, 835678, 835680, 835682, 835683, 835676, 835689
- bug list: http://bit.ly/WVEvx9
Stability
Aurora
- bug 828034 fix worked well for this and bug 829909, should land on aurora soon.
Beta
Release
- bug 806820 fix (patch in bug 831626) seems to have worked on both Nightly and Aurora, no regressions visible from it at this point.
- volume now slightly down to the weekend, but still higher than last week, 15-20% range
- Norton (bug 783369) updated 2013 and that worked, 2012 fix still coming, >5% on 18.0.1 now
Mobile
FFX:
Concern about stability for aurora...Starting to trend up again.
Mostly Flash crashes on Android OS 4+ ... unsupported flash...
bug 834213 started appearing more freqently, 1/25 and 1/29th build.
Crashers in Beta 4 to watch
Bug 800838 - Android crash in nsNPAPIPluginInstance::UnscheduleTimer @ nsNPAPIPluginInstance::TimerWithID
bug 768000 - Android Flash crash in AudioRunnable::Run
QA
- How are we going to go about PDF.js for 19?
- There are a number of bugs in this area that by themselves are not blocking, but we should evaluate user impact.
QAwanted
Verification Needed
Aurora
Beta
Mobile
Marketing/Communications
Support
- [akeybl] pdf.js and bug 836468 - "I think it might be that people aren't changing the default viewer (it's way way way too difficult)"
- Infobar for broken forms - bug 836463
- Infobar already exists for very large PDFs, German Umlauts (and other text rendering weirdness), MathML characters, etc. -- Can we check this, I don't know if the equation rendering is always giving an infobar because our examples are also large docs.
bug 836479 and bug 761539
- Fixing the infobar download behavior - bug 797288
- Embedded PDFs - no known solution when Adobe Reader availability is checked bug 836468
- Printing PDFs show a header: bug 743252
- Printing PDFs aren't as clear as Adobe.
Very little Flash CTP Feedback has come in yet, still watching. Have a user saying Norton 2013 still crashing after updates to the toolbar, will pursue and forward to relman and Norton if true
Metrics (Thu)
Roundtable
As Tuesday we talked about adding a Firefox 18.0.2 is thatattily the case or we just going to ship out 19.0.0 as planned
- How are we going to go about PDF.js for 19?