Releases/Post-mortems/Firefox 20.0

From MozillaWiki
Jump to: navigation, search

Schedule / Location / Call Information

  • Tuesday April 16, 2013 - 9 AM Pacific
  • Physical space in MV: MTV-3G Get To Da Choppa
  • Vidyo Room: ReleaseCoordination

Other communication channels

Video/Teleconference Details

  • 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

Talking Points

Timeline

20.0

  • Released on April 2, 2013 - 10% throttled
  • Got 14M ADI after ~2 days, throttled - hovered at 18M ADI

20.0.1

Firefox Desktop

  • Windows-only Non-security, user-impacting driver: bug 846848 - [OS.File] Handle UNC-formatted paths: VERIFIED FIXED in Firefox 22.0a2 and 21.0b2
  • Fallout bugs:
    • bug 857588 - Search engine list empty when the profile is on a network drive
    • bug 857672 - Address Bar not working
  • Pushed live on Thursday April 11, 2013 - unthrottled

Firefox Mobile

  • Non-security driver: bug 817775 – Marketplace promo is active on beta on about:home, but it shouldn't be
  • User-facing ridealongs:
    • bug 858561 – Move BrowserDB.expireHistory from GeckoApp.onPause to GeckoApplication.onActivityPause
    • bug 859425 – Move decoding/storing favicons to background thread
  • Pushed to Google Play on Thursday April 11, 2013

L10N

  • Issues with 21.0b2 mobile not having multilocales in the changesets checked in
  • Three human points of failure here: relman creating the json, releng verification before starting builds, qa verification of builds

Final Betas

QA

  • [DONE] Another release where we were not notified of Aurora updates being disabled. We need to be notified so we can verify and turn off our Aurora update automation in time (otherwise our system gets loaded with failures). It's a simple matter of making sure ashughes and whimboo are cc'd on the bug.
    • This has been resolved out of band between QA/RelMan/RelEng
      • Added a Bug template in Merge Documentation which can be used to file the disbale Aurora updates

RelEng

  • starting formal-20.0.0 builds earlier really helped, lets do that again FF21
    • +1 for QA
    • +1 for relman
  • Multilocale Fennec problems
  • Same version number for different changes (Fennec vs. Firefox 20.0.1 - win-only)
  • Confusion over win only vs. all platforms for FF20.0.1.
    • impact on updates for next release (FF21?)
    • [relman] Put the platform-only request in the go to build from now on

Security

Marketing

Other

  • Marketplace promo banner - better process needed around tracking the disabling of code over several releases
    • have a project in flight to land dynamic snippets for marketing messages
    • looking at FF23
    • best case is that we never hardcode again - however if marketplace is ready before dynamic is ready, it's on their team to track getting this into the correct release
  • Features that require going to beta to gather impact before ship, but not ready for immediate release:
    • All features have been required to be pref-off-able, backout-able, turning off must be clean & not impact other aspects of build
    • We don't have a good automatic mechanism for enforcing the stop (bug flags are *not* the solution here)
      • Macros currently exist for keeping features behind in nightly/aurora only (RELEASE_BUILDS)
  • Networking changes - lack of testing? What can we do moving forward to help catch these issues sooner?
    • Doug Turner taken an action to work with QA - we fail on inter-op, corner cases, integrated windows auth in this recent case, we'll require particular testing setups
    • This one was trickier because we wouldn't have known to test this area based on the change itself - our assumptions wouldn't have pointed to the networked auth issues
    • Juan asks: can we do outreach to some of these users - maybe they might try beta?

Support

  • Snippet surveys. Getting solid data, but takes 24 hours to get a survey out/turned off so we need to figure out timing.
  • Looping back to catching issues on Mobile beta channel, what went wrong here.

Notes

Actions

  • [AKEYBL]: update the meeting with the right room (MTV-3G)
  • [DONE][lsblakk] - file a bug to add android-multilocale into the default l10n-changesets.json
  • [karen] - ask Tyler & Roland watching Google play store comments every beta/release for first 24 hours - catch things like bug 861356 first comment was 4/12/2013 @4:15am - release was 4/11/2013 afternoon pacific
  • [bhearsum] - get bug 861842 fixed
  • [DONE][lsblakk] - set up a thread & process for going forward, re: burning/lockstep version numbers
  • [DONE][lsblakk] - investigate the macros & getting some for beta -- only in up to beta N, then preffed off
    • Started thread on dev-platform
  • [DONE][lsblakk] outreach to affected win-auth/unc drive users to see if they'd try beta