Firefox/Channels/Meetings/2017-09-26
Channel Meeting Details
- Tuesdays and Thursdays at 10am Pacific Time
- 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
Contents
Attendees
marcia, lizzard, kmoir,elan, philipp, jcristau, milan, dveditz, selena, RyanVM, ritu, Jean, Tom
Previous Actions
Schedule Update
Current releases dashboard: https://mozilla.github.io/delivery-dashboard
- 57 beta 3 is out! :)
- 57 mobile beta 3 to come
- 52.4.0esr-build2 signed off and ready to push to mirrors tomorrow
- More last minute 56 issues. Will build 56 again today (build 6)
- Bug 1403063 - Disable VP8 HW decoder on windows 10 (should fix a top crash)
- a sec issue
- From Fri/Mon: Not letting certain screen reader users update to 56 (JAWS/e10s issues) till new JAWS update
Timing: Marketing is asking for 9AM Pacific on Thursday
Add-ons
Shield studies
- FYI: Shield studies in flight. https://gregglind.github.io/x-shield-inflight-dashboard
Stability
[marcia]
- filed https://bugzilla.mozilla.org/show_bug.cgi?id=1402856 for missing symbols
- Apple shipped High Sierra yesterday (17A365). Actively monitoring potential crash issues.
[liz] Crashes from RC2 (56.0 build 4) release on monday: https://crash-stats.mozilla.com/search/?build_id=20170922200134&product=Firefox&version=56.0b99&date=%3E%3D2017-09-24T19%3A55%3A21.000Z&_sort=-date&_facets=signature&_columns=date&_columns=signature&_columns=product&_columns=version&_columns=build_id&_columns=platform#facet-signature
- Looks decent, not a lot of results, but OOM is on top, which means our top crashers from RC1 are probably fixed!
Nightly
awsy rate: 2.23 (browser 1.17, content 1.06)
[marcia]
- #3 top crash https://bugzilla.mozilla.org/show_bug.cgi?id=1400637 involves webroot. Fairly large number of crashes.
- New #7 top crash in stylo: https://bugzilla.mozilla.org/show_bug.cgi?id=1402589 - developer is going to get more diagnostic information
- New networking regression: https://bugzilla.mozilla.org/show_bug.cgi?id=1403154. ni on :valentin for investigation
- https://bugzilla.mozilla.org/show_bug.cgi?id=1399557 is present on both 57/58, but there are many more crashes than installs
- Bugs filed from Nightly crash triage: https://wiki.mozilla.org/NightlyCrashTriage/2017Q3
Beta
awsy rate: 0.97 (browser 0.74, content 0.23) telemetry (m+c-s) from saturday: 5.18 (week before: 5.33, this time last cycle: 4.14)
[philipp] both fixes for top crashes going into rc2 worked fine:
- gfx shutdownhangs: https://bugzilla.mozilla.org/show_bug.cgi?id=1389021
- Crash in RtlpWaitOnCriticalSection | ... | CFrameSurfaceAllocator::ReleaseDXVASurface: https://bugzilla.mozilla.org/show_bug.cgi?id=1374231
very early crash data for 57.0b3:
- Crash in mozilla::ipc::MessageChannel::WillDestroyCurrentMessageLoop: https://bugzilla.mozilla.org/show_bug.cgi?id=1398070 - ~20% of browser crashes
- has a fix that needs uplifting
- Gfx shutdownhangs: https://bugzilla.mozilla.org/show_bug.cgi?id=1402592 - ~16% of browser crashes
- IPCError-browser | PBrowserParent::RecvPDocAccessibleConstructor Constructing a top-level PDocAccessible with null COM: https://bugzilla.mozilla.org/show_bug.cgi?id=1383501 - ~15% of content crashes
Release
awsy rate: 0.86 (browser 0.62, content 0.24) telemetry (m+c-s) from saturday: 3.15 (week before: 2.90, this time last cycle: 2.53)
[marcia]
- https://bugzilla.mozilla.org/show_bug.cgi?id=1334165 is very high on release (17K crashes), but it doesn't appear after 55.
Mobile
awsy rate: release 0.66 - beta 0.77 - nightly 3.37
[marcia]
- Nightly
- Top Fennec crasher seems to be related to Activity Stream: https://bugzilla.mozilla.org/show_bug.cgi?id=1402327
- Release
- https://bugzilla.mozilla.org/show_bug.cgi?id=1394788 is still high, but has been addressed for 57 on Android
- https://bugzilla.mozilla.org/show_bug.cgi?id=1370751 also continues to be high on Android, but is a won't fix due to flash
- Beta
- Rate looks good. Some new bugs may need to be filed, but there are very few installs
Performance (Thu)
Aurora / Dev Edition
Beta
Release
QE
Nightly
Aurora / Dev Edition
Beta
Action items
Mobile
Performance
RelEng
I'm not sure if this can all be handled in the channel meeting or if we should setup a separate meeting with releng/relman
comms:
* re: marking what are the communication channels with Marketing. How can we know ahead of time for hard deadlines?
Questions for 56.0 release:
- what build will be released - firefox 56.0 build5 now build6 apparently (from status of the 56 release: At risk email thread)
- what's the expected timeframe for release? (e.g. Hour/minute/ if day is still unknown)
- what's the hard-deadline (e.g. 6:00 AM PST like last time?) - from above 9am PT
- what's the throttle rate we're aiming in the first place
- do we throttle back to 0% after 24h or have a different approach this time - we need specifics
- (from status of the 56 release: At risk email thread) Because we never had a chance to ship that to beta, we may want to throttle that release more conservatively in the first few hours, then ramp up the update rate quickly (within 6 hours) to the usual release day rate, 25%, until Friday.
- liz - 10% for 4-6 hours, then up to 25%
future planning: also would be good to know release dates and times for the other five releases in flight RELEASE IN FLIGHT: fennec 56.0 build1 2017-09-22 - thursday same as desktop RELEASE IN FLIGHT: firefox 52.4.0esr build2 2017-09-18 - from above push to mirrors tomorrow RELEASE IN FLIGHT: fennec 57.0b3 build1 2017-09-26 - Tuesday
Marketing/Communications
User Advocacy
Roundtable
- (Callek) Crash Stats Symbols for DevEdition 57... [re: r-d e-mail]
