Firefox/Planning/2013-03-06: Difference between revisions

 
(8 intermediate revisions by 6 users not shown)
Line 99: Line 99:


==== Current Releases ====
==== Current Releases ====
* {{bug|848441}} – we're going to build a custom mobile-only 19.0.1 to build a custom Gigabyte release (not pushed to the Play Store) to support a couple of their upcoming handsets and partner requirements
* {{bug|848441}} – we're going to build a custom mobile-only 19.0.1 to build a custom release (not pushed to the Play Store) to support a couple of their upcoming handsets and partner requirements


;Blog Shout Out
;Blog Shout Out
Line 113: Line 113:


*We shipped Fx20b2 to Google play: https://wiki.mozilla.org/QA/Fennec/20/Beta/2  
*We shipped Fx20b2 to Google play: https://wiki.mozilla.org/QA/Fennec/20/Beta/2  
*Fx20b3 is currently being tested and will include a fix for : https://wiki.mozilla.org/QA/Fennec/20/Beta/3
*Fx20b3 is currently being tested: https://wiki.mozilla.org/QA/Fennec/20/Beta/3
*Fx20b4 is set to include this uplift {{Bug|817828}} - (blacktab) Black area near tabs button after the URL bar is animated
*Fx20b4 is set to include this uplift {{Bug|817828}} - (blacktab) Black area near tabs button after the URL bar is animated


Line 125: Line 125:
=== Services  ===
=== Services  ===


==== Firefox Sync ====
==== Firefox Health Report ====
 
* Now enabled on Aurora for Fx21
* Android aiming for Fx22, work already landing, dependencies are tracking from {{bug|828654}}
* Working on a policy/process for future additions


==== Product Announcements  ====
==== Product Announcements  ====
* No updates, PMM on deck to start using the tool


=== Add-on SDK  ===
=== Add-on SDK  ===
Line 184: Line 190:
** Worked on webRTC bugs, including notification and styling ([https://people.mozilla.com/~jboriss/temp/webrtc_mockups/ mockups])
** Worked on webRTC bugs, including notification and styling ([https://people.mozilla.com/~jboriss/temp/webrtc_mockups/ mockups])


* '''[Click-to-play]'''
* '''[Click-to-play]''' (Larissa)
** We are doing research into redesigning Click-to-Play for non-vulnerable plugins. The results of the user research study done by Mary and Ilana are coming soon!
** We are doing research into redesigning Click-to-Play for non-vulnerable plugins. The results of the user research study done by Mary and Ilana are coming soon!
** Design ideas (currently being revised): http://people.mozilla.com/~lco/ProjectSPF/CtP/130212%20CtP%20concepts.pdf
** Design ideas (currently being revised): http://people.mozilla.com/~lco/ProjectSPF/CtP/130212%20CtP%20concepts.pdf
** prototype (courtesy of Shorlander): http://people.mozilla.com/~shorlander/files/click-to-play-prototype/clickToPlay-Mockup-03.html
** prototype (courtesy of Shorlander): http://people.mozilla.com/~shorlander/files/click-to-play-prototype/clickToPlay-Mockup-03.html


* '''[Firefox Health Report]'''
* '''[Firefox Health Report]''' (Larissa, shorlander)
** We are slowly building out the user-facing dashboard for v1 of FHR
** We are slowly building out the user-facing dashboard for v1 of FHR
*** Design: {{bug|832547}}
*** Design: {{bug|832547}}
Line 202: Line 208:
** Posted Sync setup in flyout format: [[http://invis.io/X2BV91JE click-through prototype] | {{Bug|836393}} (assigned)]
** Posted Sync setup in flyout format: [[http://invis.io/X2BV91JE click-through prototype] | {{Bug|836393}} (assigned)]
** Reviewed Options flyout tweaks: applied headline style, fixed copywriting, cleaned up [{{Bug|841686}} (fixed) | {{Bug|841511}} (fixed)]
** Reviewed Options flyout tweaks: applied headline style, fixed copywriting, cleaned up [{{Bug|841686}} (fixed) | {{Bug|841511}} (fixed)]
** Posted import browsing data UI: [{{https://bug839153.bugzilla.mozilla.org/attachment.cgi?id=713040|mockup] | {{Bug|839153}} (assigned)]
** Posted import browsing data UI: [https://bug839153.bugzilla.mozilla.org/attachment.cgi?id=713040|mockup] | {{Bug|839153}} (assigned)]
** Combined app bar under progress [{{Bug|846069}} (sketches)]
** Combined app bar under progress [{{Bug|846069}} (sketches)]
** An early stage proposal for improving the visibility of FX Metro for work within web only.[[https://www.evernote.com/shard/s153/sh/de9cee4a-3ee9-445b-a261-28ba864f661c/d1820a66ac984b551fbf583f7cb6f0c7 text-only proposal]]
** An early stage proposal for improving the visibility of FX Metro for work within web only.[[https://www.evernote.com/shard/s153/sh/de9cee4a-3ee9-445b-a261-28ba864f661c/d1820a66ac984b551fbf583f7cb6f0c7 text-only proposal]]
Line 229: Line 235:


* '''[Global UX Research for Firefox Desktop]'''
* '''[Global UX Research for Firefox Desktop]'''
** Completed market assessment of potential emerging markets. Thanks to Patrick Finch, Ria Joy, and Margaret Schroeder from the Market Research team for all their support!
** Completed market assessment of potential emerging markets. Thanks to Patrick Finch and Margaret Schroeder from the Market Research team for all their support!
** Meetings with Mozilla community members in a potential emerging markets to understand cultural, market, and technology context.
** Meetings with Mozilla community members in a potential emerging markets to understand cultural, market, and technology context.
** Planning on beginning fieldwork in May–early June.
** Planning on beginning fieldwork in May–early June.
Line 248: Line 254:
* Google also [http://blog.chromium.org/2013/02/chrome-26-beta-template-element.html unprefixed the CSS properties for transitions] and now offers support for the [http://blog.chromium.org/2013/02/chrome-26-beta-template-element.html <template> element part of Web Components]. The latter is a feature that has received significant attention from the developer community.
* Google also [http://blog.chromium.org/2013/02/chrome-26-beta-template-element.html unprefixed the CSS properties for transitions] and now offers support for the [http://blog.chromium.org/2013/02/chrome-26-beta-template-element.html <template> element part of Web Components]. The latter is a feature that has received significant attention from the developer community.
* The company also open-sourced [http://googledevelopers.blogspot.ca/2013/02/compress-data-more-densely-with-zopfli.html Zopfli, a deflate-compatible, compress-only replacement for zlib that offers 3-8% better compression levels]
* The company also open-sourced [http://googledevelopers.blogspot.ca/2013/02/compress-data-more-densely-with-zopfli.html Zopfli, a deflate-compatible, compress-only replacement for zlib that offers 3-8% better compression levels]
* Chrome Beta for Android now offers support for http://blog.chromium.org/2013/03/data-compression-in-chrome-beta-for.html SPDY-based proxy browsing]. The service compresses traffic, serves it all via SSL, replaces DNS lookups, and transcodes all images to the WebP format. Chrome for Android now also syncs all passwords and form autofill entries between desktop and mobile browser.
* Chrome Beta for Android now offers support for [http://blog.chromium.org/2013/03/data-compression-in-chrome-beta-for.html SPDY-based proxy browsing]. The service compresses traffic, serves it all via SSL, replaces DNS lookups, and transcodes all images to the WebP format. Chrome for Android now also syncs all passwords and form autofill entries between desktop and mobile browser.
* Chrome Stable now supports the [http://chrome.blogspot.ca/2013/02/bringing-voice-recognition-to-web.html Web Speech API], with a nice Chrome-only [https://www.google.com/intl/en/chrome/demos/speech.html demo].
* Chrome Stable now supports the [http://chrome.blogspot.ca/2013/02/bringing-voice-recognition-to-web.html Web Speech API], with a nice Chrome-only [https://www.google.com/intl/en/chrome/demos/speech.html demo].
* Chrome has also disabled [http://chrome.blogspot.ca/2013/02/bringing-voice-recognition-to-web.html  silent extension installs], [http://chrome.blogspot.ca/2013/02/bettar-spell-chek-in-chrome.html improved their spell checking to support grammar, homonym, and context-sensitive checking], a [http://chrome.blogspot.ca/2013/02/race-to-win-on-big-and-small-screens.html web game that can be controlled by up to four Chrome for Android devices], and [http://chrome.blogspot.ca/2013/03/faster-browsing-for-your-smaller-screens.html improved their Octane Javascript performance by 25%].
* Chrome has also disabled [http://chrome.blogspot.ca/2013/02/bringing-voice-recognition-to-web.html  silent extension installs], [http://chrome.blogspot.ca/2013/02/bettar-spell-chek-in-chrome.html improved their spell checking to support grammar, homonym, and context-sensitive checking], a [http://chrome.blogspot.ca/2013/02/race-to-win-on-big-and-small-screens.html web game that can be controlled by up to four Chrome for Android devices], and [http://chrome.blogspot.ca/2013/03/faster-browsing-for-your-smaller-screens.html improved their Octane Javascript performance by 25%].
*  Chrome OS has [http://src.chromium.org/viewvc/chrome?view=rev&revision=183955 increased the priority of tabs which are playing audio], making it less likely that they will be discarded in low memory situations. [http://src.chromium.org/viewvc/chrome?view=rev&revision=184183 Tabs which are playing audio will now have a visual indicator displaying the volume], making it a lot easier to determine where these random sounds are coming from.
*  Chrome OS has [http://src.chromium.org/viewvc/chrome?view=rev&revision=183955 increased the priority of tabs which are playing audio], making it less likely that they will be discarded in low memory situations. [http://src.chromium.org/viewvc/chrome?view=rev&revision=184183 Tabs which are playing audio will now have a visual indicator displaying the volume], making it a lot easier to determine where these random sounds are coming from.
==== HTML5 ====
==== HTML5 ====
* A survey by HTML5 tools vendor [http://www.kendoui.com/blogs/teamblog/posts/13-02-26/html5_vs_native_vs_hybrid_global_developer_survey_2013_results_are_in.aspx Kendo UI] found that 50% of developers developed HTML5 apps in 2012, but 90% plan to in 2013, and that only 15% of developers would do "native-only" development.
* A survey by HTML5 tools vendor [http://www.kendoui.com/blogs/teamblog/posts/13-02-26/html5_vs_native_vs_hybrid_global_developer_survey_2013_results_are_in.aspx Kendo UI] found that 50% of developers developed HTML5 apps in 2012, but 90% plan to in 2013, and that only 15% of developers would do "native-only" development.
Line 285: Line 292:


== Questions, Comments, FYI  ==
== Questions, Comments, FYI  ==
* Jeff would like to know who would be involved eliminating the fx old locale betas from the bottom of [https://www.mozilla.org/en-US/firefox/all.html https://www.mozilla.org/en-US/firefox/all.html]?
* Jeff & Axel (l10n) would like to know who should be involved in eliminating the fx old locale betas from the bottom of [https://www.mozilla.org/en-US/firefox/all.html https://www.mozilla.org/en-US/firefox/all.html]? Also, L10n Drivers will be in Mountain View & San Francisco from March 17 - 22 for l10n workweek.


== Actions this week  ==
== Actions this week  ==

Latest revision as of 00:54, 23 January 2014

« 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.


Actions from Last Week

Schedule & Progress on Upcoming Releases

Firefox Desktop

Current Releases

  • Pwn2Own starts today so we have point people for all areas of a release should a 19.0.2 chemspill become necessary this week

Beta (128)

  • 20.0b3 went to build yesterday, last beta for taking speculative fixes goes to build Tues March 12th in the morning

Aurora (54)

Nightly (129)

Firefox Metro

Project Performance

  • From Iterations #1 - #2:
    • Total Points Completed: 62
    • Total Stories Closed: 11
    • Team Point Velocity: 31 per iteration
    • Average Stories Closed: 5.5 per iteration
    • Average Point Closure Rate: 29% per iteration
    • Scope Change (Defects and Changes): 17 points over 7 stories
  • Story Backlog: 26 stories ready for upcoming iterations.
  • Legacy Backlog: 6 stories remaining for QA testing.
  • On Hold Backlog: 4 stories remaining for Product Manager clarification before being moved into Story Backlog.
  • Planning Backlog: 33 stories for Team to review, relate to work items and assign point values.
Iteration #1
  • Iteration Points
    • Committed = 102
    • Completed = 30
    • Closure Rate = 29.4%
  • Scope Change
    • New Defects Generated = 0
    • New Changes Generated = 3 points over 1 story
Iteration #2
  • Iteration Points
    • Committed = 110
    • Completed = 32
    • Closure Rate = 29.1%
  • Scope Change
    • New Defects Generated = 4 points over 2 stories
    • New Changes Generated = 10 points over 4 stories

Iteration #3 - In Progress

  • Team Commitment: 72 points over 12 stories
  • Progress To Date:
    • 22 points completed over 7 stories.
    • 30.5% closure rate on points.
    • 50 points over 5 stories remain to complete iteration.

Iteration #4 - Upcoming

Firefox Mobile

Current Releases

  • bug 848441 – we're going to build a custom mobile-only 19.0.1 to build a custom release (not pushed to the Play Store) to support a couple of their upcoming handsets and partner requirements
Blog Shout Out
Post-MWC Work week in London!
  • Lot's of excellent brainstorms, discussions, hack sessions. One of the themes for today was our continued obsession with improving performance and responsiveness. UX improvements, expanding measurements and benchmarks were all discussed and solid next steps were documented to make the ideas actionable.
  • General agenda: https://intranet.mozilla.org/Mobile_Team_Meet_Up_March_2013#Agenda
  • Expect lot's of interesting news once the team is back to their home offices next week

Beta (128)

Aurora (54)

  • We're buttoning this release up in time for beta readiness on April 2nd
  • We welcome any feedback regarding how our new web content fonts (Open Sans and Charis) are looking on your favorite websites, do chime in and relate any bugs you file to: bug 831354

Nightly (129)

  • NFC sharing landed bug 726335 - Use NDEF Push with NFC (Android Beam | API level 14) for transferring currently focused tab

Services

Firefox Health Report

  • Now enabled on Aurora for Fx21
  • Android aiming for Fx22, work already landing, dependencies are tracking from bug 828654
  • Working on a policy/process for future additions

Product Announcements

  • No updates, PMM on deck to start using the tool

Add-on SDK

Release (1.13.2 -> Firefox 19, 20)

Stabilization (1.14 -> Firefox 20, 21)

Development (Firefox 22)

  • remaining Firefox 21 PWPB work should be completed by EOW, but has taken longer than expected.
  • blog post about PWPB support & issues in the SDK
  • Dev Tools team ( including Jetpack ) are in beautiful downtown Sunnyvale next week for a work week, so no audible, etc.

Feedback Summary

Desktop

Win 8 Crashes: Reports of crashes are steadily going down on Win 8 after the 19.01 release
PDF.js: Feedback is stable as well. No new critical issues to report. Big thanks to pdf.js team for all the great work.

  • The new PDF viewer is bloody marvellous - massively improves my internet experience to have a lightweight alternative to Adobe. Job well done.
  • I really like the PDF reader! Been using Firefox since before version 1.0! Keep up the good work! -JC
  • I LOVE the new builtin PDF rendering. Awesome! So fast! So safe!

Firefox 19 Sentiment Report: Available next week.

Mobile

We are tracking slowness on JB+ devices on input.

We have a new autotagger system! We are currently working on growing and expanding the tools we have at our disposal. Expect more details soon.

User Experience (Design & Research)

Do not panic! These updates have been sparse in the run-up to MWC, so this is a "Best of Firefox UX updates" list for the last month.

  • [desktop]
    • [misc]
      • Consolidating our papercuts/axe-wounds lists; new reddit "tell us your issues" thread planned for later this week (limi, bwinton)
    • [Australis] (Zhenshuo, Shorlander)
    • [Social API] (Boriss)
      • Worked with team on menu design, language, UI for next phases of patches (mockups, some also done in meetings & whiteboards)
      • Met with developers & F1 designers, sketched next iteration as share panel design
      • Worked on solutions to multi-provider & switching in next versions (mockups)
    • [newtab2] (Boriss)
      • Planned with research (particularly Cori, Gregg, and Ilana) what data could be gathered to help inform design, including from previous work and current MicroPilot study on Multi-search (etherpad on needed data)
      • Moved designs for testing ahead, with collaboration with bizdev (presentation), research, and engagement, currently incorporating updates to in-page Australis content (planning doc,schedule)
      • Worked with Blake Winton on prototyping for testing (one version under active dev)
      • Researched alternatives to thumbnails for testing, iterated with bclark, decided to test with Junior-style brand-centric messaging
  • [GuM/webRTC] (Boriss)
    • Worked on webRTC bugs, including notification and styling (mockups)
  • [Behavioral Segmentation Study (Project Meta)] (Lindsay, Bill, Leo)
    • Quantitative study is complete. We had 1000 respondents to our survey. We are currently analyzing the results and will be finish the analysis this week.
    • Next steps:
      • Realign user types based on quantitative results.
      • Report and presentations. There will be a Brownbag presentation to Mozilla at-large and a presentation to the UX team in early April.
  • [Global UX Research for Firefox Desktop]
    • Completed market assessment of potential emerging markets. Thanks to Patrick Finch and Margaret Schroeder from the Market Research team for all their support!
    • Meetings with Mozilla community members in a potential emerging markets to understand cultural, market, and technology context.
    • Planning on beginning fieldwork in May–early June.
    • Meeting with stakeholders to finalize 2–3 primary global emerging markets in which to conduct qualitative UX and product research in 2013.
    • Meeting with potential partner research firms who have logistical expertise in primary global emerging markets.

Market Insights from the Product Marketing Strategy Team

Desktop / Platform

Google

HTML5

  • A survey by HTML5 tools vendor Kendo UI found that 50% of developers developed HTML5 apps in 2012, but 90% plan to in 2013, and that only 15% of developers would do "native-only" development.

Microsoft

Opera

  • Opera skipped version 13 and went directly to Opera Beta 14 for Android for the new WebKit-based version of their browser. Initial reviews have been positive, both for performance and for the inclusion of a "Discover" curated content discovery tool. Some of the first WebKit patches from Opera engineers also landed.

Canonical / Ubuntu

Security

WebKit

W3C

Marketing, Press & Public Reaction

Desktop Marketing

  • Marketshare holds "steady as a rock" at 20% for February. 
  • Mobile World Congress: It's now over! As you've heard it was a huge sucess. Top WebRTC question: "When will it be available on Android?"
  • Other Desktop Projects: Speaking to SEO vendors, Social API multi-provider planning, ongoing release planning


Questions, Comments, FYI

  • Jeff & Axel (l10n) would like to know who should be involved in eliminating the fx old locale betas from the bottom of https://www.mozilla.org/en-US/firefox/all.html? Also, L10n Drivers will be in Mountain View & San Francisco from March 17 - 22 for l10n workweek.

Actions this week