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
Attendees
marcia, RyanVM, elan,cornel, Julia,Cristian, philipp, petruta, ninu, Sorina, rares, lmandel, roxana, Tom, Timea, selena, poiegas, mtabara, rail, kmoir, bsurd
Previous Actions
Schedule Update
Current releases dashboard: https://mozilla.github.io/delivery-dashboard
56.0 is NEARLY out the door
- locale WNP issues, looking
- 57b4 go to build in a few hours
- Still going through the list of uplifts
Add-ons
Shield studies
- FYI: Shield studies in flight. https://gregglind.github.io/x-shield-inflight-dashboard
Stability
change of shutdownhang signature generation since yesterday with https://bugzilla.mozilla.org/show_bug.cgi?id=1402037
Nightly
awsy rate: 6.05 (browser 1.09, content 4.96)
[marcia]
- Nightly rate has increased since Tuesday.
- Top Crash https://bugzilla.mozilla.org/show_bug.cgi?id=1400637 has over 5K crashes. Related to security sandboxing
- Top crash https://bugzilla.mozilla.org/show_bug.cgi?id=1403154 ->
mozilla::dom::PerformanceNavigationTiming::Type had thousands of crashes (over 7K between the various signatures) but is now resolved fixed
- https://bugzilla.mozilla.org/show_bug.cgi?id=1383501 has few installs but over 1300 crashes. It is an accessibility related crash
- Linux crash https://bugzilla.mozilla.org/show_bug.cgi?id=1399978 has been fixed
- New Mac/Linux crash https://bugzilla.mozilla.org/show_bug.cgi?id=1403932 related to a webextensions checkin
Beta
awsy rate: 1.29 (browser 0.89, content 0.40) telemetry (m+c-s) from tuesday: 4.33 (week before: 4.94, this time last cycle: 3.89)
[philipp] a fifth of beta users got updated to 57.0b so far
top browser crashers in 57.0b3:
- Crash in mozilla::ipc::MessageChannel::WillDestroyCurrentMessageLoop: https://bugzilla.mozilla.org/show_bug.cgi?id=1398070 - 25% of browser crashes
- fix landed for b4
- Shutdownhangs in mozilla::layers::CompositorThreadHolder::Shutdown: https://bugzilla.mozilla.org/show_bug.cgi?id=1402592 - 19.5% of browser crashes
- has a patch pending approval for beta
- Crashes in Intel's igdusc64.dll module: https://bugzilla.mozilla.org/show_bug.cgi?id=1403353 - 16% of browser crashes
- fix in progress - bug has a reviewed patch
- Crashes in mozilla::a11y::AccessibleWrap::GetIAccessibleFor: https://bugzilla.mozilla.org/show_bug.cgi?id=1379951 - 0.65% of browser crashes
top content crashes in 57.0b3:
- Crash in IPCError-browser | PBrowserParent::RecvPDocAccessibleConstructor Constructing a top-level PDocAccessible with null COM: https://bugzilla.mozilla.org/show_bug.cgi?id=1383501 - 24% of content crashes
- Crash in mozilla::EMEDecryptor::Init: https://bugzilla.mozilla.org/show_bug.cgi?id=1401922 - 5.4% of content crashes
- fix landed for b4
- Crash in nsINode::IsEditableInternal: https://bugzilla.mozilla.org/show_bug.cgi?id=1403841 - 4.7% of content crashes
Release
awsy rate: 0.86 (browser 0.61, content 0.25) telemetry (m+c-s) from tuesday: 3.03 (week before: 2.95, this time last cycle: 2.59)
[marcia]
- Nothing of note to call out.
Mobile
awsy rate: release 0.66 - beta 0.93 - nightly 2.76
- https://crash-stats.mozilla.com/signature/?signature=ResolvePromise#summary affects Android and Desktop, and is fairly high. See comment in Beta Section
[marcia]
- Nightly
- https://bugzilla.mozilla.org/show_bug.cgi?id=1402327 is top crash in nightly and #12 in beta as well. Looks as if it will be fixed by Bug 1402145
- Beta
- https://bugzilla.mozilla.org/show_bug.cgi?id=1347984 is top beta crash and seems stuck at the moment. See comment from Till
- #5 top crash is https://bugzilla.mozilla.org/show_bug.cgi?id=1403787 - Firefox accounts related and marked a P1 and assigned
- Release
- https://bugzilla.mozilla.org/show_bug.cgi?id=1382335 is high on release but has been addressed for 56
Performance (Thu)
Aurora / Dev Edition
Beta
Release
QE
[Cornel]
- 56.0 RC (build6) signed off with no issues.
- WNP testing on 56RC (release-cdntest) completed
- report: https://public.etherpad-mozilla.org/p/wnp-fx56 - clarification needed for a couple of locales (ar, gl, az, he and gu-IN)
- ESR 52.4-build2 signed off as GREEN.
Nightly
Aurora / Dev Edition
Beta
57.0b3 signed off with 4 new (low-impact) issues - GREEN.
Action items
Mobile
- Ioana will be in SF/MV for the next two weeks - working from mozilla offices - ping her if you are around ( she plans to meet with mostly all around the area)
- RC 56.0 signed off without one low-impact issue: https://wiki.mozilla.org/QA/Fennec/56/RC/smoketests-results
- Beta 57.0b3 signed off with 3 new issues: https://wiki.mozilla.org/QA/Fennec/57/Beta/3/smoketests-results
Ioana is sorry for the interrupt
Performance
RelEng
Marketing/Communications
User Advocacy
Roundtable
- [RyanVM] Concerns about missing symbols from DevEdition 57b1/b2 builds and overall crash rate monitoring during that week
- No monitoring on the Socorro side for crash reports that it can't symbolicate (has also burned us on OSX previously)
- Crash stats dashboards didn't really have the DevEdition rates anywhere obvious
- Calling DevEdition version b0 makes it hard to discern trends between versions
- Marco C worked on that, we (RM) have some alerts, we can extend that
- (callek) Task Configuration Change https://bugzilla.mozilla.org/show_bug.cgi?id=1403970 is one option to reduce the chance of missing this when creating or modifying jobs.
• READ ONLY [elan] We have three quick-turnaround product integrity requests for SV from the Shield team, you should be seeing requests soon:
1) enrollment add-on (Pioneer related) 2) 57 satisfaction survey (must get deployed during 56 Release) 3) Search related experiment
- READ ONLY [selena] milan is asking for us *not* to update any Windows 7 Pre-SP1 with 64-bit -- catlee asked us to notify liz
- that wn't be happening till next week anyway at the earliest , talk with romain and cpeterson ok great thanks
- mtabara - RelEng automation needs some buffer time to update all resources and propagate. I think we should not block the release on WNP issues. We can tackle that after