From MozillaWiki
Jump to: navigation, search
« previous week | index | next week »

Channel Meeting Details

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
These notes are read by people who weren't able to attend the meeting. Please make sure to include links and context so they can be understood.

Previous Actions

Schedule Update

  • Firefox Desktop & Android 29 beta 6 built


  • No updates.



  • bug 740325 (_cairo_surface_snapshot_copy_on_write) has sharply spiked on 30 and 31 starting on 2014-04-04, can be reproduced internally, people are on it.
  • bug 984358 (PNG encoder) is waiting for checkin on aurora.


  • FIXED in 29.0b5:
    • bug 988548 (Graphics) - looks like the fix helped, its signatures are gone from the top 300 in 29.0b5 \o/
    • bug 987531 (xtls.dll) has dropped off sharply without our doing anything.
  • WAITING for beta landing:
    • bug 976536 (JIT/GC) is waiting for uplift approval (now #1 on 29.0b5).
      • probably also fixes bug 988961 (InitFromBailout), will need to watch data.
  • WAITING for approval requests:
    • bug 987248 (part of the Seer problems) landed on trunk.
    • bug 856796 (Yarr) is correlated to Avast, some discussion happening now, workaround patch existing.
    • bug 976181 (nsContentUtils::IsCallerChrome) is probably a dupe of bug 913138, which has patches up for review.
    • bug 970362 Sylvestre has emailed F-secure 3 times, and we have a reply now, they forwarded it to engineers internally.





GGC crashes currently account for 9.39% (1859 crashes in the last week)

  • Known bugs:
    • Top-sites like Soundcloud and Google Maps are prominently affected
    • QA is working with Engineering to investigate these crashes
  • More instable than Nightly is used to? Is it impacting our ability to collect good feedback?
    • QA suggests turning it off until the current known crashers can be fixed, leaning toward leaving it on Nightly for at least one more cycle
    • Engineering suggests waiting until the last week of Nightly to decide

(Lukas has tracked the bugs for 31 so we can keep an eye out before merge)




  • QA has completed testing 29b6



User Advocacy

Feedback is worthless right now for anything technical. Sorry.

Thunderbird (Tue)

Metrics (Thu)


  • Strategy on the 29 release:
    • SUMO: Articles, putting hot topics up at the top
    • QA: Any additional help pointing people to input/bugzilla if they land on QA first?
    • Addons: Featured addons all work with Australis right?
    • Press & Marketing: Any additional posts? Press on release day we can tweet/share/amplify?
    • Planned Tuesday April 29th at 8am PT
    • Will be staying at 10% throttled (as normal) and check in before unthrottle on the Sync load
    • If we can get feedback at that point too, perhaps we slow releasing the updates (wait longer to unthrottle)
  • crash/stability cross-channel: bug 973138 (__fnNCDESTROY) has been low top 10 in rank for some time now, blocklisting is pretty hard as we'd need to add support for wildcards to DLL blocklisting, and then it would be a whack-a-mole job still. We need a relman decision on if we should put in the large amount of implementing the wildcard blocklisting support.
  • FF 28 Post Mortem

Talking Points



  • Released Desktop & Mobile on time even with 5 Pwn2Own issues found (all fixed)

28.0.1 Mobile

  • Released on March 24, 2014 for bug 963612 - H.264 video playback on several Galaxy devices

Firefox Desktop

  • Lost several key features for not being ready (Gamepad API, input number/color)

Firefox Mobile


Final Beta being RC

  • We had to skip this because of Pwn2Own turnaround time - did not end up hitting the AMD crash with the builds, thankfully



  • Metro backout was communicated far too late, increased RC churn+1 (and unavoidable by our teams, at least)
  • WebVTT was not known to QA until Beta and only then by accident, ended up pref'd off (not in release notes either - unusual for such a large feature)
  • Safe Browsing changes were not clearly communicated to QA before release
    • Matt Wobensmith is working with Monica to prevent this in the future
  • Communication around Pwn2Own was done extremely well, led to a lot of clarity around what needed to be tested and when
  • Additional QA resources, better triage processes, better cross-team communication (including additional focus on Aurora and Nightly) allowed us to improve our verification rate by 30% and confirmation rate by 80%
  • Data suggests that BitGuard crash bug 985922 might block affected 27.0.1 users from updating to 28 via the update mechanism, what should we do there?
    • The crash itself will only be fixed for 29->30 updates by better blocklisting, so 28->29 will still see it.


  • most stable release in a long while 1.4 crashes/100ADU






  • No issues that we could have caught
  • We may not be able to run a snippet survey in 28 again (for obvious reasons)




  • Getting features on QA & relman radar -- need to talk with dev-planning/fx-team/PM team about how we know something significant is coming [lukas]
  • [lukas] how many users are still on 27.0.1?
  • Contact some 27.0.1 users to ask them if they can update to 28 or not? [Kairo, emails to Cheng]