Firefox/Channels/Meetings/2016-05-31
Channel Meeting Details
- Tuesdays and Thursdays at 10am Pacific Time
- irc.mozilla.org #planning for backchannel
- Past meeting notes: https://wiki.mozilla.org/Firefox/Channels/Meetings
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
Contents
Attendees
calixte, marcia, philipp, ritu, lmandel, jst, davidb, rmcguigan, kbrosnan, lizzard, blassey
Previous Actions
Schedule Update
Add-ons
Stability
crash data from elasticsearch is unreliable at the moment - https://bugzilla.mozilla.org/show_bug.cgi?id=1276690
Aurora
overall rate: 1.64 (orange), browser: 1.16, content: 0.48
overall crash rate is on par with that of the last cycle at this time - though content crashes are significantly lower (~0.2) & shutdownhangs are higher (0.2)
- biggest issue in danger of moving to beta is shutdownhang in mozilla::layers::CompositorBridgeParent::ShutDown (regressing in 48) https://bugzilla.mozilla.org/show_bug.cgi?id=1268559
- this is actively worked on
Beta
overall rate: 1.16 (orange), browser: 0.96, content: 0.19
crash rate (for the browser-process) is about 0.15 lower than in the 46 rc week
crash fixes that have gone into beta 9:
- shutdownhang in nsThread::Shutdown https://bugzilla.mozilla.org/show_bug.cgi?id=1258009 -> signature still present, not sure if it has reduced though (due to the ES data issue)
- crash in TppTimerpExecuteCallback https://bugzilla.mozilla.org/show_bug.cgi?id=1270686 -> signature gone (by disabling d3d11 dxva) \o/
- crash in _dwrite_draw_glyphs_to_gdi_surface_gdi https://bugzilla.mozilla.org/show_bug.cgi?id=726206 -> looks fixed as well
Release
overall rate: 0.96 (greenish orange) startup crashes: 0.13, shutdownhangs: 0.2
- no new concerns
Nightly
- https://bugzilla.mozilla.org/show_bug.cgi?id=1276295 was causing a crash on Mac, but was quickly backed out
- https://bugzilla.mozilla.org/show_bug.cgi?id=1229252 is still hanging around, but I have an update from the developer in Comment 72
- https://wiki.mozilla.org/Platform/Uptime/Logs has the Uptime team logging information
Mobile
- Beta stability looks good
- Nightly crash that is greatly affecting the crash rate https://bugzil.la/1271103 - crash in GL code with several signatures
Release Health report
We (relman, also sheriffs) should check for test permafails well before the merge. Track them or mark as blockers if they should block the next merge. (usually works to search on "permafail", sort by last changed, and skim: https://bugzilla.mozilla.org/buglist.cgi?quicksearch=permafail&list_id=13046716 )
nightly 49: 3 blockers, 30 new regressions aurora: 3 blockers, 103 new regressions beta: 0 blockers, 20 new regressions (true number is 14)
- These bugs should block release. Are these bugs moving?
release: 2 blockers, 11 new regressions (Blockers = potential ridealongs)
Performance (Thu)
Aurora / Dev Edition
Beta
Release
QE
Nightly
Aurora / Dev Edition
Beta
Action items
Mobile
Performance
RelEng
Marketing/Communications
User Advocacy
Roundtable
- Fx47 owners for potential dot release during London work week
- RelEng rep TBD
- Sheriff TBD
- Ritu from relman
Special Topics
Aurora/Beta Feature Review
Post-Mortem (Tues 2wks from GA Release)
Sign Off (Thurs prior to GA Release)
Actions