Firefox/Planning/2014-04-09

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

Planning Meeting Details

  • Wednesdays - 11:00am PT, 18:00 UTC
  • Mountain View Offices: Warp Core Conference Room
  • Toronto Offices: Finch Conference Room
  • irc.mozilla.org #planning for backchannel
  • (the developer meeting takes place on Tuesdays)

Video/Teleconference Details - NEW

  • 650-903-0800 or 650-215-1282 x92 Conf# 99696 (US/INTL)
  • 1-800-707-2533 (pin 369) Conf# 99696 (US)
  • Vidyo Room: ProductCoordination
  • Vidyo Guest URL
REMEMBER
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.

FORCETOC

Actions from Last Week

Schedule & Progress on Upcoming Releases

Firefox Desktop & Platform

Current Releases

Beta (57)

Aurora (54)

Nightly (58)

Firefox Mobile

Current Releases

Beta (57)

Aurora (54)

Nightly (58)

Developer Tools

  • Jeff is @TRIBE this week, everything seems fine.

Feedback Summary

Desktop

Mobile

UX & User Research

Market Insights from the Market Strategy Team

Desktop/Platform

  • Support for Windows XP ended with roughly 27% of Windows users still using it [1], around 76% of IT Pros supporting it, [2] 95% of ATMs still using it pending hardware upgrades. [3] With no further updates to Internet Explorer on Windows XP and support for Chrome on Windows XP ending April 2015, [4], the preferred secure browser for systems running Windows XP is an evolving space.
  • As Google Chrome adds support for new capabilities such as ephemeral mode [5] and password manager updates [6], the Chromium framework is utilized as a platform for building browsers [7] which in some cases cut down features to improve privacy and speed. [8]
  • A research report titled "Cookies that give you away" [9] illustrates how an eavesdropper can use multiple third-party cookies to link about 50% of a user’s history to the same pseudonymous ID even with just 25% of the current density of trackers on the web and then link to a real-life ID exposed on the Web. In the absence of third-party tracking cookies, the attacker's ability would be severely circumscribed by changes in the user's IP address. Methods of tracking users that block third-party cookies include HTTP redirect, [10] persistent and unblockable cookies, [11] and history extraction,[12] which are not impossible to execute, but add more complexity.

Marketing, Press & Public Reaction

Questions, Comments, FYI

Actions this week