Releases/Post-mortems/Firefox 24.0

From MozillaWiki
Jump to: navigation, search

Schedule / Location / Call Information

  • Tuesday October 1st, @ 9:00 am PT
  • Physical room(s):
    • MV - Get to da Choppa
    • TOR - TOR5N Spadina
  • Vidyo Room: Release Coordination
  • Back Channel - #planning

Other communication channels

  • irc.mozilla.org #planning for back channel
  • This etherpad for real-time notes (we'll copy the wiki page in at the beginning of the meeting, and out at the end)

Previous Actions (from FF23)

  • joduinn to investigate desktop repack - channel changing
  • bsmedberg to run his script on build#1 crash data
    • if we can find it, then we'll continue making build #2 automatically
    • if we can't find it, then we'll stop making build #2 and make more dot releases :(
  • lsblakk to create meeting about RC instead of beta 10
  • lsblakk to speak to Laura about finding out about putting in a tab for users about a specific change - timing, finding out sooner - what causes/guidelines about when to do this
    • One of those last minute request from Asa for Metro
  • need to create a tstore/yandex email process
  • lsblakk speak to Chad about Sam replacement for mobile content (Play Store) -- get owner for each store. Jesse Montano is our new product marketing contractor dedicated to mobile. Keep Chad in the loop, but Jesse will be gathering and updating this content. (will Jesse be doing GooglePlay only, or is Jesse also doing Yandex + TStore?) I expect GPlay, too, once he is ramped up (TStore is probably going to be the last to be added to his list: his prio will be GPlay then Yandex then they can figure out with Spinger how to handle the TStore)
  • lsblakk - check with Axel if having a hook on l10n repos for key/visible string would help protect localization teams from errors like [fr] tools in the future
    • especially for string *changes*
  • lsblakk - add User Advocacy to the Release Note Feature review meeting

Talking Points

Timeline(s)

24.0

Final Betas

Desktop

  • Final Beta (Fx24 Beta #10) push out on Sep 10 as targeted

Mobile

  • Did a build #2 on Sep 11 for final beta due to
    • Bug 899159 - Upstream issues with OpenSLES audio code in webrtc ( a webrtc issue)

QA

Mobile QA

RelEng

  • Bug 908134 - Figure out how to offer release build to beta users, Releng anythingn ew to report here ?
    • on list for FF26
  • FF24.0b1
    • win32 pymake/l10n problems delayed beta1 for 5? days
    • linux, mac builds and updates fine
    • win32 localized builds found broken in wild.
    • FF24.0b2 was fine
    • TB problem / lightning also
      • Releng to-do a fake release two weeks prior to beta 1 go-to-build
      • Last two weeks of aurora, no changes to make files,build config changes
  • Permission requirements for android (issue happened on Fx25)
    • Have a check two weeks earlier
    • akeybl to meet with Brad to discuss opyions
      • Permission hook ?
      • Have a check on builds two weeks prior to beta
      • QA to front loading permission check

Security

Marketing & Press

Stability

  • Norton: Update with crash fixes for 2014.* versions went out today, 2013.* should follow within a day.
    • Crash volume going down as expected

Mobile

User Advocacy

Still seeing a couple Norton crashes but no spike in feedback around unthrottling like expected -- it's still really early. Support article is getting some light traffic (data coming tomorrow). Still working with metrics on a process for getting info about how many people have certain extensions enabled: data we got quickly was unreliable/completely wrong. Apparently we have issues with pulling data from FHR (?). Cheng is working with anurag on this. In general, we need a faster turnaround on data after release when bad things happen. First 25-50 responses in the release survey were terrible (Easily 0.5-1 star lower than usual)... probably just a weird glitch but we'll investigate.

24.0 esr and 17.0.9esr

Other

Actions

  • Bug 908134 - Figure out how to offer release build to beta users, Releng anythingn ew to report here ? - follow-up in channel meeting
  • Laura - Fold in Metro into normal marketing discussion
  • lsblakk - check with Axel if having a hook on l10n repos for key/visible string would help protect localization teams from errors like [fr] tools in the future
    • especially for string *changes*
  • [bajaj] Follow up with metrics on getting "right" numbers faster atleast post release
Retrieved from "https://wiki.mozilla.org/index.php?title=Releases/Post-mortems/Firefox_24.0&oldid=719043"