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

Channel Meeting Details

  • Tuesdays at 10am PDT, and Thursday at 2:00pm PDT
  • Mountain View Offices: Warp Core Conference Room
  • #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
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.

Channel Meeting Details

  • Tuesdays at 10am PDT, and Thursday at 2:00pm PDT
  • Mountain View Offices: Warp Core Conference Room
  • #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

Previous Actions

CTP Rollout Discussion

  • CTP issues
    • bug 800018 – Click-to-play is broken on various websites like or (2nd round)
    • bug 809846 – Click to Play doesn't play music
  • (may be a dup of bug 800018)
  • (affects advertising, doesn't look like a big deal)
  • (social network) music player
  • music player... see bug 809846 for details, may be a dup of bug 800018, may be a separate issue with nested frames
  • prompts people to try their "beta HTML5 version" for a flash-free experience. If you click fast enough after load in the address bar, you can make the Flash version work too.

Options: 1. Delaying CTP launch until 18/ESR17.0.1. due to risky late-landing and test day findings of additional sites affected -- still need whitelisting when it's time to ship but buys us more time to prepare & test 2. Whitelisting only without late-landing of 800018. How easy to add additional broken sites when discovered? 3. Uplifting 800018 today, shipping (and testing) in b6 and hoping it does reduce known issues on our side, but we will still need whitelisting at the same time for when our hands are tied on a particular site (eg: Pandora) 4. Do nothing and use CTP in 17.0. No longer an option, given broken sites like Pandora that would require new solutions. 5. Don't CTP block Flash, block [current plan: old vulnerable at first, ratchet up over time] Java/Silverlight/etc., maybe take 800018, don't whitelist. And then do option 1 in the future. Decisions:

  • Don't want to maintain a CTP whitelist given the prevalence of sites that play audio
  • Don't want to ship a Flash CTP blocklist while hidden audio players are completely unusable (from a user's perspective)
  • We'll file a bug to resolve hidden audio players like Pandora, and include Asa/UX in this process
    • Flashblock solution: Click to Play block in top-left corner
    • show the door-hanger from the blue lego block instead of requiring a click
      • possibly on a timer, so it goes away fairly quickly on its own
    • something more clever UX can come up with?
  • We'll move forward with previously planned non-Flash blocklists
  • We'll make the other infobar blocks version specific
  • We'll land 800018 in FF18/ESR17.0.1
  • We need a support article, on the front page, about broken plugins (for Java/Silverlight/etc.)
  • Option 5

Schedule Update

  • 17 Beta 5 pushed live
  • 17 Beta 6 will go to build Monday, targeting EOD PT
  • 17 Beta 6 will ship next Wednesday, and the merge from m-b to m-r should occur shortly after
  • Shooting for a go to build for the final 17 build between 10AM and 12 PT
  • [juanb] Stub-installer?
  • [ashughes] esr10, esr17 go-to-build? esr10 on thurs, esr17 on friday with 17.0




   Version:  11.5.502.113 of flash is showing up in crash stats

Windows 8

   F21225463 showing up as a top signature in the Windows 8 report but needs a bug. Happens with Win 7 as well


   Aurora crash rates look pretty good ATM

Beta needs to go to someone who works with the JS debugger - it and the duplicate signature are high in the Mac beta crashes - Old spiking on beta and other branches
   New bug filed from explosive report: - #10 top crash overall



  • We need to watch ARMv6 closely when we release it - no blocking concerns so far, but it's hard to tell if minor concerns we have will become larger ones or not.





  • Monitoring of l10n repack failures on Aurora
    • One solution: bug 800432 – Email Axel & release-mgmt about l10n issues with builds on mozilla-aurora [Action RelEng - enable these emails before next merge day (20 cycle) 01/07/2013?]
    • Timeline: sooner the better
  • Release builds for 17.0 will need ARMv6 - confirm configs & branding ready (for 17, yes? - yes)
  • Need list of locales for What's New page before go-to-build (nov 16) bug 807836
    • [ACTION: Lforrest to provide]
  • Confirm that there will be no updates TO 17.0esr
    • no, we will update to 17.0.2 (as long as no chemspill)


  • bug 807836 – Show What's New page for Firefox 17.0 updates
    • Firm go/no-go coming on Monday
    • ask for earlier decision from Sheila & co. so we have time if there's a code change


  • [akeybl] ARMv6 feedback post-release
    • Tyler taking point on this -- keeping an eye out on our advertised devices especially. Great to get a rollup on Wed, pre-thanksgiving, then after, and then go to weekly (to same list of people as weekly mobile)

Social API Feedback Lots of praise [1]:

   I am happy because the new Facebook Messenger is AWESOME! 
   The new facebook messenger is very good.  A quick way to keep up to date with facebook 
   Awesome feature in fb chat messenger, especially when you're  busy with  another website and want to chat with friends without opening  fb tab,  thank you FireFox! 

Popular Issues:

    Many users have trouble disabling the feature [2] [3] Bug on file [4]. 
    A spike in unable to connect issues yesterday [5]
   there was an outage on FB end -- it was rectified with their server push last night
    Slowness with sidebar active [6] [7]
   memory issues can be added to

General Implementation Feedback:

   Unminimizing chats in Facebook Messenger Social app does not put focus in text chat popup's entry box 
   Minimised Facebook chat in Messenger plugin obstructs search input box on Facebook site sidebar 
   Clicking on links in facebook messenger opens them *inside* the popup :( 
   Whenever using Social API with the Facebook Messenger App you  should  disable the Native Facebook Messenger while accesing the  Facebook  Website because they get over each other and gets confusing 
    Whenever I roll the mouse over a link the link description on  the  "status bar" appears over the facebook messenger app (Social api).  You  should reallocate the link description when using Social API. 

Facebook's Help Page:

Thunderbird (Tue)

Metrics (Thu)

  • Windows breakdown by driver versions for bug 806346


  • Reminder: MozCamp, Thanksgiving, and Holiday coverage


  • akeybl to email about CTP decision
  • catlee to follow up on bug 800432
  • catlee to kick off beta/release stub installers
  • lsblakk will follow up on above stability issues for beta
  • tyler to provide armv6 feedback a day after release, and then a week after release


Aurora Queries

Beta Queries