Attendees
KaiRo, lizzard, lmandel, rrayborn, kbrosnan, ritu, jlund
Schedule Update
- 41
- RC1 build1 pushed to Beta channel
- Fennec beta10 sign off done, will upload to play store shortly
- Remaining items
- Bug 1204796 – RC build of Firefox 41 displays the wrong version string
- Bug 1194923 – Crash in mozilla::layers::CompositorOGL::BindAndDrawQuads
- Bug 1204324 – Crash in nsXMLHttpRequest::Send(nsIVariant*, mozilla::dom::Nullable<T> const&) rising in 41.0b9
- RC2 gtb Wed/Thursday
- question on l10n stuff: affiliate code for yahoo search plugin https://bugzilla.mozilla.org/show_bug.cgi?id=1200170
- We did take an l10n change on 09/11 specific to Japanese locale.
- Confirmed that Flod pushed this https://bugzilla.mozilla.org/show_bug.cgi?id=1200170#c8
- ESR gtb was yesterday, will ask for softvision to spot check
- status of 38.3.0
- release-automation emails: https://groups.google.com/a/mozilla.com/forum/?hl=en#!topic/release-automation-notifications/u6PWRsaZXFU%5B126-150%5D
- go to the last page and look for most recent completed jobs
- you can see that antivirus and update-verify jobs are complete. this is how releng can tell that we are ready to push to esr-cdn-test (mirrors). However we usually wait for a r-d email to explicitly say ‘push Firefox $version $buildnum to esr-cdntest channel’ before we move forward
- wiki: https://wiki.mozilla.org/Releases/Firefox_38.3.0esr/BuildNotes
- so we are currently on this step: https://wiki.mozilla.org/Release:Release_Automation_on_Mercurial:Updates#Push_to_mirrors
- release-automation emails: https://groups.google.com/a/mozilla.com/forum/?hl=en#!topic/release-automation-notifications/u6PWRsaZXFU%5B126-150%5D
- status of 38.3.0
Thanks. This was just me not seeing the emails (gmail search issue, 38.3.0 gave me nothing but 38.3.0esr got me all the notifications. – liz
Add-ons
- No updates.
Stability
Aurora
- Overall rate: 1.7 (target: <1.5) – browser: 1.0, content: 0.7
- Switching off e10s by default made us drop to the same rates as 41 had before uplift to beta.
- No signature did rise significantly, so nothing really bad happened to non-e10s mode as far as we can tell on the stability side.
Beta
- Overall rate: 0.9 (same as last week)
- bug 1204324 (nsXMLHttpRequest::Send) is a new crash (#1 Top Crash Score, 0.7% of b9 crashes) triggered by some add-ons, worked around for the moment by blocklisting the two most-seen add-ons, but there are more that trigger this. The bug is clearly in our code and not the add-ons as JS-only add-ons should never make us crash in a way like that. The add-ons that we blocked were not signed, so we didn’t see them trigger this before we turned off the signing requirement.
- bug 1182197 (Promise Settle) is 1.9% of 41.0b9 crashes. Took a speculative fix in RC1
- bug 1204909 (TraceCallbackFunc::Trace) is a new crash with 0.4% but 3.7 crashes per installation, so pretty annoying to those who encounter it.
Release
- Overall rate: 0.9 (same as last week)
- bug 1189940 continues to be ~15% of Windows 10 crashes.
- bug 1198884 (ubuntu, GStreamer 1.0) is still by far the #1 crash on Linux, the actual crash is probably bug 1112371
Mobile
- bug 1194923 is a pretty bad issue on Nexus 6 and similar devices, might be a 41 blocker
- bug 1204483 is a new crash in beta, though it seems to happen on unusual devices
User Advocacy
No updates
Special Topics
Post-Mortem (Tues 2wks from GA Release)
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: ReleaseCoordination
- Vidyo Guest URL