MozillaWiki - User contributions [en]

Engagement/Developer Engagement/BrowserIDPlan/Weekly Meetings

2012-07-05T19:55:29Z

Lmesa:

=== Persona Dev Engagement Meeting Notes ===
* [https://etherpad.mozilla.org/PersonaDevEngage-7-05-12 7-05-12]
* [https://etherpad.mozilla.org/PersonaDevEngage-6-26-2012 6-26-2012]
* [https://etherpad.mozilla.org/PersonaDevEngage-6-19-2012 6-19-2012]
* [https://etherpad.mozilla.org/PersonaDevEngage-6-12-2012 6-12-2012]
* [https://etherpad.mozilla.org/PersonaDevEngage-6-5-2012 6-5-2012]
* [https://etherpad.mozilla.org/PersonaDevEngage-5-29-2012 5-29-2012]
* [https://etherpad.mozilla.org/PersonaDevEngage-5-15-2012 5-15-2012]
* [https://etherpad.mozilla.org/PersonaDevEngage-5-8-2012 5-8-2012]
* [https://etherpad.mozilla.org/PersonaDevEngage-5-3-2012 5-3-2012]

Engagement/Developer Engagement/BrowserIDPlan/Weekly Meetings

2012-06-26T17:10:11Z

Lmesa:

=== Persona Dev Engagement Meeting Notes ===
* [https://etherpad.mozilla.org/PersonaDevEngage-6-26-2012 6-26-2012]
* [https://etherpad.mozilla.org/PersonaDevEngage-6-19-2012 6-19-2012]
* [https://etherpad.mozilla.org/PersonaDevEngage-6-12-2012 6-12-2012]
* [https://etherpad.mozilla.org/PersonaDevEngage-6-5-2012 6-5-2012]
* [https://etherpad.mozilla.org/PersonaDevEngage-5-29-2012 5-29-2012]
* [https://etherpad.mozilla.org/PersonaDevEngage-5-15-2012 5-15-2012]
* [https://etherpad.mozilla.org/PersonaDevEngage-5-8-2012 5-8-2012]
* [https://etherpad.mozilla.org/PersonaDevEngage-5-3-2012 5-3-2012]

Engagement/Developer Engagement/BrowserIDPlan/Weekly Meetings

2012-06-19T17:39:14Z

Lmesa:

=== Persona Dev Engagement Meeting Notes ===
* [https://etherpad.mozilla.org/PersonaDevEngage-6-19-2012 6-19-2012]
* [https://etherpad.mozilla.org/PersonaDevEngage-6-12-2012 6-12-2012]
* [https://etherpad.mozilla.org/PersonaDevEngage-6-5-2012 6-5-2012]
* [https://etherpad.mozilla.org/PersonaDevEngage-5-29-2012 5-29-2012]
* [https://etherpad.mozilla.org/PersonaDevEngage-5-15-2012 5-15-2012]
* [https://etherpad.mozilla.org/PersonaDevEngage-5-8-2012 5-8-2012]
* [https://etherpad.mozilla.org/PersonaDevEngage-5-3-2012 5-3-2012]

Engagement/Developer Engagement/BrowserIDPlan/Weekly Meetings

2012-06-12T17:38:17Z

Lmesa:

=== Persona Dev Engagement Meeting Notes ===
* [https://etherpad.mozilla.org/PersonaDevEngage-6-12-2012 6-12-2012]
* [https://etherpad.mozilla.org/PersonaDevEngage-6-5-2012 6-5-2012]
* [https://etherpad.mozilla.org/PersonaDevEngage-5-29-2012 5-29-2012]
* [https://etherpad.mozilla.org/PersonaDevEngage-5-15-2012 5-15-2012]
* [https://etherpad.mozilla.org/PersonaDevEngage-5-8-2012 5-8-2012]
* [https://etherpad.mozilla.org/PersonaDevEngage-5-3-2012 5-3-2012]

Firefox/Channels/Meetings/2012-06-07

2012-06-07T20:39:49Z

Lmesa: /* Marketing/Communications */

Firefox/Channels/Meetings/2012-06-07

2012-06-07T19:32:07Z

Lmesa: /* Marketing/Communications */

Firefox/Channels/Meetings/2012-06-07

2012-06-07T19:20:01Z

Lmesa: /* Marketing/Communications */

Firefox/Planning/2012-06-06

2012-06-06T18:26:47Z

Lmesa: /* Marketing */

<center>[[Firefox/Planning/{{#time: Y-m-d | {{SUBPAGENAME}} -1 week}}|« previous week]] | [[Firefox/DeliveryMeetings|index]] | [[Firefox/Planning/{{#time: Y-m-d | {{SUBPAGENAME}} +1 week}}|next week »]]</center>

'''Planning Meeting Details'''
* Wednesdays - 11:00am PDT, 18:00 UTC
* Mountain View Offices: Warp Core Conference Room
* Toronto Offices: Finch Conference Room
* [irc://irc.mozilla.org/planning irc.mozilla.org #planning] for backchannel
* (the [[Platform#Meetings|developer meeting]] takes place on Tuesdays)

'''Video/Teleconference Details - NEW'''
* 650-903-0800 or 650-215-1282 x92 Conf# '''95312''' (US/INTL)
* 1-800-707-2533 (pin 369) Conf# '''95312''' (US)
* Vidyo Room: Warp Core
* Vidyo [https://v.mozilla.com/flex.html?roomdirect.html&key=UK1zyrd7Vhym Guest URL]

{{Notes}}

__FORCETOC__

== Actions from Last Week ==

== Schedule & Progress on [[Releases|Upcoming Releases]] ==
=== Kilimanjaro ===

===Firefox Desktop ===
==== Release (13, 10esr, <strike>3.6</strike>) ====
* FF13 released yesterday! Full unthrottling will wait till after Patch Tuesday next week.
* We pulled the final lever for moving insecure 3.6 users up to mainline - note the strike-out in the title

==== Beta (14) ====
* FF14b6 will be released tomorrow (6/7)

==== Aurora (15) ====
* Aurora 15 updates will be enabled Friday

==== Nightly (16) ====
* A big thanks to Marco Castelluccio for implementing a Web Apps Runtime and native install for Web apps for desktop Linux. With Marco's contribution, we will be able to support native web apps on Windows, Mac, and Linux for Kilimanjaro and beyond.
** Bug 745018 - Implement webapp runtime for Linux
** Bug 744193 - Install web app on host OS - Linux
* PDF.js is making great progress
** Bug 752676 - Control pdf.js and Other PDF Plugins using Application Preferences
** Bug 742099 - Localize pdf.js strings and replace with the final strings for release
* Bug 749628 - Implement a "Responsive Design" tool
* Bug 758812 - Break up browser.js into smaller pieces, Phase 1
* Bug 735099 - Re-enable incremental GC on desktop platforms

=== Firefox Mobile ===
====Beta (14)====
* Prepping Beta 6, XF for tablets and FN for phones

====Aurora (15)====
* Tablet UI
* Reading List
* Find in Page

====Nightly (16)====
* Search Suggestions
* Chromeless WebApps
* Text Selection in Web Content

=== Services ===
==== Firefox Sync ====
* nothing major to report
* Native Sync is fleshing out ui parity (on Nightly)

==== Apps In the Cloud Server ====
* nothing major to report

=== Add-on SDK ===

[https://groups.google.com/d/topic/mozilla-labs-jetpack/buwPODIj3SQ/discussion Released 1.8b4!]

No other updates this week due to Add-ons mini-workweek

===Identity===
* Work is progressing, drop by #identity or ping Ben A. for a demo of a (working!) Firefox-native sign in email chooser
* On track for 16

===Apps===
* Firefox Desktop 14 (Beta) - landed
** Functionality was backed out - {{bug|750936}}
** Native Install
** Chromeless launch of apps

* Firefox Desktop 15 (Aurora)
** Features: Support of native installation and and chromeless launch of apps for Win and Mac OS

* Firefox Desktop 16 (Nightly)
** Fit and polish for K9o requirements

* Firefox Mobile 15 (Nightly) - in progress
** Features: Native Install and chromeless window launch
** Proposed marketplace bundling with Fennec is an open issue. See {{bug|738545}}

* Apps in the Cloud
** AITC client for desktop landed for FF15

===Developer Tools/Experience===
* Firefox 15 (Aurora)
** Debugger
*** includes remote debugging for Fennec
*** need to watch Aurora feedback closely
** Responsive Mode
*** Mentioned last month, preffed on last week
*** Test responsive layouts without resizing your whole browser
** Layout view
*** Added to Style Inspector
*** Shows at-a-glance metrics like height, width, padding for the selected element
** Developer toolbar will be on the next train.
* End-to-end Apps tutorial draft
** there's [https://developer.mozilla.org/en/Apps/Tutorials/General a draft on MDN]
** this content will be presented directly on the Marketplace site
* Prototype of [http://jlongster.github.com/mortar/ Open Web Apps Bootstrap] up

== Feedback Summary ==
=== Desktop ===
* Firefox 13: Generally OK feedback so far, comments mainly around new features. Most of the negative comments could be addressed through user education.
==== Issues ====
We are seeing a 3% decrease in issues for 13 compared to the first two days of Firefox 12. Currently we are seeing reports of the following:

* SPDY cannot connect to Gmail on XP SP3 issue [https://support.mozilla.org/en-US/questions/928731]
* Avast claims FF 13 update is suspicious [https://support.mozilla.org/en-US/questions/928699]
* Possibly something with hotmail/messenger (Can't change status, can't log in, can't read messages -- lots of pt-BR messages)
* Slower than previous versions [http://input.mozilla.org/en-US/?product=firefox&sentiment=sad&date_end=2012-06-06&date_start=2012-06-05&version=13.0&q=slow]
* Memory consumption [http://input.mozilla.org/en-US/?product=firefox&sentiment=sad&date_end=2012-06-06&date_start=2012-06-05&version=13.0&q=memory]

New tab page (probably about 60% negative): [http://input.mozilla.org/en-US/?product=firefox&version=13.0&date_start=2012-06-05&date_end=2012-06-06&q=new+tab]:
* Want home page [http://input.mozilla.org/en-US/opinion/2981756] [http://input.mozilla.org/en-US/opinion/2980702] [http://input.mozilla.org/en-US/opinion/2981195]
* Want google [http://input.mozilla.org/en-US/opinion/2981923]
* Don't know how to disable [http://input.mozilla.org/en-US/opinion/2981815]
* Don't know how to manage links [http://input.mozilla.org/en-US/opinion/2981794]
* Think it is a privacy issue [http://input.mozilla.org/en-US/opinion/2981439] - about 40-50% of negative feedback about this feature.

Tabs on demand:
* Don't know how to disable [http://input.mozilla.org/en-US/opinion/2981830]

Home page (about 80% negative):
* Almost universally hated because some people (a number of people) seem to have lost their previous home pages. Also, can't set "blank" as a home page.
* Reset the home page [http://input.mozilla.org/en-US/opinion/2979945]
* Unable to change homepage [http://input.mozilla.org/en-US/opinion/2981845]
* Don't like the new buttons [http://input.mozilla.org/en-US/opinion/2981767]
* Users can't change the search engine on this page.
* Some users are ending up with Yahoo as a home page without their consent.

==== Praise ====

New Tab Page [http://input.mozilla.org/en-US/?product=firefox&sentiment=happy&date_end=&date_start=&version=13.0&q=new+tab]:
* Dear Firefox, I absolutely adore the history thumbnails that appear now whenever I open a new browser or a new tab. Thanks!!
* I really love the new tab feature added with your latest update!
* The new tab page makes it much easier to get to your favorite websites.

Homepage [http://input.mozilla.org/en-US/?product=firefox&sentiment=happy&date_end=&date_start=&version=13.0&q=%28home+page%29|%28homepage%29]:
* Awesome mozilla firefox 13 with new features off home page.A lot of improvements.Good job by your team.
* Buttons on the bottom of the homepage- handy

Smooth scrolling [http://input.mozilla.org/en-US/?product=firefox&sentiment=happy&date_end=&date_start=&version=13.0&q=Scroll]:
* Smooth scrolling !!! FINALLY !
* Nice and smoth scroll option.. sss ..
* Smooth scrolling looks very good and faster. thanks!

=== Mobile ===
Firefox Beta for Android fixed the top three user issues with the product (start-up performance, browsing performance and flash support).

Overall for beta4/5 feedback is good; 4 stars.

Beta4/5 user issues:
*Photon 4g continues to generate low reviews
*A couple of instability reports and a couple of website incompatibility reports (techcrunch)

Beta 4/5 requests:
*Text selection
*Fewer permissions

Documentation:
*Completing documentation of single sync client requirement for beta/aurora/nightly users before installing release
*Updating supported devices documentation
*Need to update language support documentation
*Need to clarify tablet support and compatibility

== UX & User Research ==
=== UX Design ===

* UX summit last week, so we were quiet
* [hometab/newtab] new mockups getting finished for some lightweight prototyping (Boriss)
* [android] (ibarlow)
** final bug work for Native UI release (so soon!)
** tablet and next-version-of-phone implementation and design support going on in
*** {{bug|739355}} - Title bar updates (tablet and phones)
*** {{bug|739364}} - Awesomebar updates (tablet and phones)
*** {{bug|739407}} - Tab menu updates (tablet and phones)
*** {{bug|713450}} - Close tabs by slide
** Oh look! First traces of search suggest designs landing [http://www.flickr.com/photos/lucasrocha/7160434745/ screenshot in flickr]
* [sync setup] [http://cl.ly/1t3U0o1J1e3h2U2N1g2N 90% use case flow revisions] (Zhenshuo)
* [Identity] Ongoing design of Sign-into-site flows - [http://people.mozilla.com/~zfang/PersonaID/PersonaIDNative1.jpg variant 1], [http://people.mozilla.com/~zfang/PersonaID/PersonaIDNative2.jpg variant 2] (Zhenshuo)
* [apps integration] Design of app recommendations ongoing (Boriss, with special guest Bryan)
* [desktop]
** Reviewing Australis designs against new [https://blog.mozilla.org/ux/2012/06/firefox-heatmap-study-2012-results-are-in/ Firefox heatmap data] (Zhenshuo)
** Detailed interaction design iterations happening on Australis customization UI; [http://people.mozilla.com/~shorlander/files/customization-interactive-mockup-panel/customizationInteractiveMockup-panel.html basic clickable mockup] (Zhenshuo, Stephen)
** Design in progress for layout of in-content preferences: [http://people.mozilla.com/~zfang/Preferences/InContentPreferences.jpg mockup] (Zhenshuo)
* [metro] (Yuan)
** User feedback on button styling for metro app bar -- [http://people.mozilla.com/~ywang/FX%20on%20Metro/ user test materials]
** Another video sketch, this one about general web browsing use, in preparation
** Exploring share functions, through app contract

=== Research ===
UR ran some usability tests on the Firefox Beta. We found that basic tasks (search, bookmarking, tabs) were easy for participants to complete. There are some questions around the search accelerators in the Top Sites tab, and of course typing is still painful. UR will work with UX to figure out how to manage. Anyone who wants to see raw video footage of the tests can contact Mary Trombley.

== '''Market Insights''' ==
=== Desktop / Platform ===
==== Apple ====
* Apple was granted [http://da.feedsportal.com/c/34438/f/628517/s/200bc187/l/0L0Spatentlyapple0N0Cpatently0Eapple0C20A120C0A60Capple0Ewins0Epatents0Efor0Eindustrial0Edesign0Efuture0E3d0Eremote0Eharnessing0Epower0Ethrough0Eelectromagnetic0Einduction0Bhtml/ia1.htm 22 patents] covering everything from industrial design to a futuristic 3D Apple TV remote and even a way that Apple envisions of harnessing power through electromagnetic induction to help extend battery life on iOS devices.
==== Microsoft ====
* The 6th Platform Preview for IE10 [http://blogs.msdn.com/b/ie/archive/2012/05/31/windows-release-preview-the-sixth-ie10-platform-preview.aspx now includes] the latest preview update for IE10. It includes an embedded Adobe Flash Player, which has been improved to support touch gestures. It is also integrated with the Process Lifetime Manager to better improve battery life in the Metro environment. Flash will also be bundled with the operating system and will receive improvements through Windows Update.
* The new release preview also sends a Do Not Track header by default, the first web browser to do so.
* IE10 now supports unprefixed versions of CSS transitions, transforms, animations, gradients, and CSS Fonts’ font-feature-settings property, as well as platform APIs such as the Indexed Database API (IndexedDB) and requestAnimationFrame().
* IE10 will also [http://blogs.msdn.com/b/ie/archive/2012/06/04/legacy-dx-filters-removed-from-ie10-release-preview.aspx no longer support] IE4's visual filters and transitions for anything other than intranet sites
* Interesting, Microsoft is going to great lengths to force adoption of the Metro-style interface, even to the point of [http://venturebeat.com/2012/05/31/windows-8-start-button-2 removing all code from Windows 8 referencing the Start button/menu] to prevent third-party developers from creating a workaround allowing people to continue using it
* Microsoft's Bing Mobile team released [https://www.onx.ms/#!findOutMorePage On-Ex], an Android application that is a sort of "if this then that" for mobile phones. Powered by Javascript, it offers some interesting API calls -- [https://www.onx.ms/#apiPage/modeOfTransport modeOfTransport] returns whether the user is walking, running or driving.
* Analysts are estimating that new Windows RT tablets will be in the [http://computerworld.co.nz/news.nsf/technology/windows-rt-tablets-could-cost-500-to-700 $500-$700 price range], which raises concerns for their viability

==== Google ====
* Fully hardware-accelerated CSS filters [http://blog.chromium.org/2012/06/accelerated-css-filters-landed-in.html are available in Chrome/Chromium version 19 and newer]
* The press are heralding the upcoming Chrome version 21 as being optimized for [http://www.geek.com/articles/geek-pick/google-chrome-21-gears-up-for-gaming-20120530/ web-based gaming]
==== Security ====
* [http://krebsonsecurity.com/2012/05/facebook-takes-aim-at-cross-browser-lilyjade-worm Facebook is trying to stop a browser plugin-based worm] that uses the Crossrider cross-platform plugin creation tool.
==== Tizen ====
* A Tizen developer ran the [http://www.tizenexperts.com/2012/05/tizen-lord-rings-ringmark-facebook/ RingMark test] on Tizen, Android, and iPhone smartphones. Tizen was the clear leader with 141 passed Ring 1 tests.
==== Gaming ====
* The authors of Scirra, an HTML5 gaming framework, [http://www.scirra.com/blog/85/the-great-html5-mobile-gaming-performance-comparison did an HTML5 desktop/mobile gaming shootout using 23 different combinations of browsers and devices]. Firefox got the highest score for desktop but the lowest for Android 4.0.

=== Mobile ===

Summary below, full update [http://irinasandu.com/2012/06/06/android-and-mobile-browsing-insights-week-23/ here] and in your inbox.

* Opera announced it reached 189.6 million mobile users, a new version of Opera Mini for basic phones and a partnership with America Movil and one with Bharti Airtel

* 65% of all Androids run Gingerbread, 19% Froyo and 7% Ice Cream Sandwich

* The hardware section of the Play Store expansing with accessories

* Researchers found security flaws in Google Bouncer

* HTC and Sony partnered to augment their mobile offerings

* First Android device on x86 architecture available in Europe

* Samsung Galaxy S III landing in market, Galaxy Note 2 rumoured to launch in October

* Asus, Acer and Toshiba to be among Windows 8 tablet manufacturers

* Video of Tizen on Samsung reference device [http://www.tizenexperts.com/2012/05/hands-tizen-developer-prototype-device/ available]

* By 2015 smartphones will account for 75% of new phones sold

== Marketing, Press & Public Reaction ==

==== Marketing ====

* Finalizing materials for releases later this week; getting started on the next round of releases.
* LMesa and GJimenez finishing handoff to LForrest; LForrest to take lead in earnest next week.

==== Press ====

*[http://www.pcworld.com/businesscenter/article/256886/six_good_reasons_to_download_firefox_13.html Six Good Reasons to Download Firefox 13] 
*[http://www.webmonkey.com/2012/06/firefox-13-a-faster-smarter-web-browser/ Firefox 13: A Faster, Smarter Web Browser] 
*[http://www.webpronews.com/firefox-13-releases-a-day-before-official-launch-2012-06 Firefox 13 Releases A Day Before Official Launch] 
*[http://blogs.cio.com/browsers/17135/firefox-13-arrives-snazzy-features-rival-chrome Firefox 13 Arrives with Snazzy Features that Rival Chrome] 

 

== Questions, Comments, FYI ==
* If you see :gps, give him a giant hug, or a beer.

== Actions this week ==

Firefox/Planning/2012-06-06

2012-06-06T18:25:31Z

Lmesa: /* Marketing, Press & Public Reaction */

<center>[[Firefox/Planning/{{#time: Y-m-d | {{SUBPAGENAME}} -1 week}}|« previous week]] | [[Firefox/DeliveryMeetings|index]] | [[Firefox/Planning/{{#time: Y-m-d | {{SUBPAGENAME}} +1 week}}|next week »]]</center>

'''Planning Meeting Details'''
* Wednesdays - 11:00am PDT, 18:00 UTC
* Mountain View Offices: Warp Core Conference Room
* Toronto Offices: Finch Conference Room
* [irc://irc.mozilla.org/planning irc.mozilla.org #planning] for backchannel
* (the [[Platform#Meetings|developer meeting]] takes place on Tuesdays)

'''Video/Teleconference Details - NEW'''
* 650-903-0800 or 650-215-1282 x92 Conf# '''95312''' (US/INTL)
* 1-800-707-2533 (pin 369) Conf# '''95312''' (US)
* Vidyo Room: Warp Core
* Vidyo [https://v.mozilla.com/flex.html?roomdirect.html&key=UK1zyrd7Vhym Guest URL]

{{Notes}}

__FORCETOC__

== Actions from Last Week ==

== Schedule & Progress on [[Releases|Upcoming Releases]] ==
=== Kilimanjaro ===

===Firefox Desktop ===
==== Release (13, 10esr, <strike>3.6</strike>) ====
* FF13 released yesterday! Full unthrottling will wait till after Patch Tuesday next week.
* We pulled the final lever for moving insecure 3.6 users up to mainline - note the strike-out in the title

==== Beta (14) ====
* FF14b6 will be released tomorrow (6/7)

==== Aurora (15) ====
* Aurora 15 updates will be enabled Friday

==== Nightly (16) ====
* A big thanks to Marco Castelluccio for implementing a Web Apps Runtime and native install for Web apps for desktop Linux. With Marco's contribution, we will be able to support native web apps on Windows, Mac, and Linux for Kilimanjaro and beyond.
** Bug 745018 - Implement webapp runtime for Linux
** Bug 744193 - Install web app on host OS - Linux
* PDF.js is making great progress
** Bug 752676 - Control pdf.js and Other PDF Plugins using Application Preferences
** Bug 742099 - Localize pdf.js strings and replace with the final strings for release
* Bug 749628 - Implement a "Responsive Design" tool
* Bug 758812 - Break up browser.js into smaller pieces, Phase 1
* Bug 735099 - Re-enable incremental GC on desktop platforms

=== Firefox Mobile ===
====Beta (14)====
* Prepping Beta 6, XF for tablets and FN for phones

====Aurora (15)====
* Tablet UI
* Reading List
* Find in Page

====Nightly (16)====
* Search Suggestions
* Chromeless WebApps
* Text Selection in Web Content

=== Services ===
==== Firefox Sync ====
* nothing major to report
* Native Sync is fleshing out ui parity (on Nightly)

==== Apps In the Cloud Server ====
* nothing major to report

=== Add-on SDK ===

[https://groups.google.com/d/topic/mozilla-labs-jetpack/buwPODIj3SQ/discussion Released 1.8b4!]

No other updates this week due to Add-ons mini-workweek

===Identity===
* Work is progressing, drop by #identity or ping Ben A. for a demo of a (working!) Firefox-native sign in email chooser
* On track for 16

===Apps===
* Firefox Desktop 14 (Beta) - landed
** Functionality was backed out - {{bug|750936}}
** Native Install
** Chromeless launch of apps

* Firefox Desktop 15 (Aurora)
** Features: Support of native installation and and chromeless launch of apps for Win and Mac OS

* Firefox Desktop 16 (Nightly)
** Fit and polish for K9o requirements

* Firefox Mobile 15 (Nightly) - in progress
** Features: Native Install and chromeless window launch
** Proposed marketplace bundling with Fennec is an open issue. See {{bug|738545}}

* Apps in the Cloud
** AITC client for desktop landed for FF15

===Developer Tools/Experience===
* Firefox 15 (Aurora)
** Debugger
*** includes remote debugging for Fennec
*** need to watch Aurora feedback closely
** Responsive Mode
*** Mentioned last month, preffed on last week
*** Test responsive layouts without resizing your whole browser
** Layout view
*** Added to Style Inspector
*** Shows at-a-glance metrics like height, width, padding for the selected element
** Developer toolbar will be on the next train.
* End-to-end Apps tutorial draft
** there's [https://developer.mozilla.org/en/Apps/Tutorials/General a draft on MDN]
** this content will be presented directly on the Marketplace site
* Prototype of [http://jlongster.github.com/mortar/ Open Web Apps Bootstrap] up

== Feedback Summary ==
=== Desktop ===
* Firefox 13: Generally OK feedback so far, comments mainly around new features. Most of the negative comments could be addressed through user education.
==== Issues ====
We are seeing a 3% decrease in issues for 13 compared to the first two days of Firefox 12. Currently we are seeing reports of the following:

* SPDY cannot connect to Gmail on XP SP3 issue [https://support.mozilla.org/en-US/questions/928731]
* Avast claims FF 13 update is suspicious [https://support.mozilla.org/en-US/questions/928699]
* Possibly something with hotmail/messenger (Can't change status, can't log in, can't read messages -- lots of pt-BR messages)
* Slower than previous versions [http://input.mozilla.org/en-US/?product=firefox&sentiment=sad&date_end=2012-06-06&date_start=2012-06-05&version=13.0&q=slow]
* Memory consumption [http://input.mozilla.org/en-US/?product=firefox&sentiment=sad&date_end=2012-06-06&date_start=2012-06-05&version=13.0&q=memory]

New tab page (probably about 60% negative): [http://input.mozilla.org/en-US/?product=firefox&version=13.0&date_start=2012-06-05&date_end=2012-06-06&q=new+tab]:
* Want home page [http://input.mozilla.org/en-US/opinion/2981756] [http://input.mozilla.org/en-US/opinion/2980702] [http://input.mozilla.org/en-US/opinion/2981195]
* Want google [http://input.mozilla.org/en-US/opinion/2981923]
* Don't know how to disable [http://input.mozilla.org/en-US/opinion/2981815]
* Don't know how to manage links [http://input.mozilla.org/en-US/opinion/2981794]
* Think it is a privacy issue [http://input.mozilla.org/en-US/opinion/2981439] - about 40-50% of negative feedback about this feature.

Tabs on demand:
* Don't know how to disable [http://input.mozilla.org/en-US/opinion/2981830]

Home page (about 80% negative):
* Almost universally hated because some people (a number of people) seem to have lost their previous home pages. Also, can't set "blank" as a home page.
* Reset the home page [http://input.mozilla.org/en-US/opinion/2979945]
* Unable to change homepage [http://input.mozilla.org/en-US/opinion/2981845]
* Don't like the new buttons [http://input.mozilla.org/en-US/opinion/2981767]
* Users can't change the search engine on this page.
* Some users are ending up with Yahoo as a home page without their consent.

==== Praise ====

New Tab Page [http://input.mozilla.org/en-US/?product=firefox&sentiment=happy&date_end=&date_start=&version=13.0&q=new+tab]:
* Dear Firefox, I absolutely adore the history thumbnails that appear now whenever I open a new browser or a new tab. Thanks!!
* I really love the new tab feature added with your latest update!
* The new tab page makes it much easier to get to your favorite websites.

Homepage [http://input.mozilla.org/en-US/?product=firefox&sentiment=happy&date_end=&date_start=&version=13.0&q=%28home+page%29|%28homepage%29]:
* Awesome mozilla firefox 13 with new features off home page.A lot of improvements.Good job by your team.
* Buttons on the bottom of the homepage- handy

Smooth scrolling [http://input.mozilla.org/en-US/?product=firefox&sentiment=happy&date_end=&date_start=&version=13.0&q=Scroll]:
* Smooth scrolling !!! FINALLY !
* Nice and smoth scroll option.. sss ..
* Smooth scrolling looks very good and faster. thanks!

=== Mobile ===
Firefox Beta for Android fixed the top three user issues with the product (start-up performance, browsing performance and flash support).

Overall for beta4/5 feedback is good; 4 stars.

Beta4/5 user issues:
*Photon 4g continues to generate low reviews
*A couple of instability reports and a couple of website incompatibility reports (techcrunch)

Beta 4/5 requests:
*Text selection
*Fewer permissions

Documentation:
*Completing documentation of single sync client requirement for beta/aurora/nightly users before installing release
*Updating supported devices documentation
*Need to update language support documentation
*Need to clarify tablet support and compatibility

== UX & User Research ==
=== UX Design ===

* UX summit last week, so we were quiet
* [hometab/newtab] new mockups getting finished for some lightweight prototyping (Boriss)
* [android] (ibarlow)
** final bug work for Native UI release (so soon!)
** tablet and next-version-of-phone implementation and design support going on in
*** {{bug|739355}} - Title bar updates (tablet and phones)
*** {{bug|739364}} - Awesomebar updates (tablet and phones)
*** {{bug|739407}} - Tab menu updates (tablet and phones)
*** {{bug|713450}} - Close tabs by slide
** Oh look! First traces of search suggest designs landing [http://www.flickr.com/photos/lucasrocha/7160434745/ screenshot in flickr]
* [sync setup] [http://cl.ly/1t3U0o1J1e3h2U2N1g2N 90% use case flow revisions] (Zhenshuo)
* [Identity] Ongoing design of Sign-into-site flows - [http://people.mozilla.com/~zfang/PersonaID/PersonaIDNative1.jpg variant 1], [http://people.mozilla.com/~zfang/PersonaID/PersonaIDNative2.jpg variant 2] (Zhenshuo)
* [apps integration] Design of app recommendations ongoing (Boriss, with special guest Bryan)
* [desktop]
** Reviewing Australis designs against new [https://blog.mozilla.org/ux/2012/06/firefox-heatmap-study-2012-results-are-in/ Firefox heatmap data] (Zhenshuo)
** Detailed interaction design iterations happening on Australis customization UI; [http://people.mozilla.com/~shorlander/files/customization-interactive-mockup-panel/customizationInteractiveMockup-panel.html basic clickable mockup] (Zhenshuo, Stephen)
** Design in progress for layout of in-content preferences: [http://people.mozilla.com/~zfang/Preferences/InContentPreferences.jpg mockup] (Zhenshuo)
* [metro] (Yuan)
** User feedback on button styling for metro app bar -- [http://people.mozilla.com/~ywang/FX%20on%20Metro/ user test materials]
** Another video sketch, this one about general web browsing use, in preparation
** Exploring share functions, through app contract

=== Research ===
UR ran some usability tests on the Firefox Beta. We found that basic tasks (search, bookmarking, tabs) were easy for participants to complete. There are some questions around the search accelerators in the Top Sites tab, and of course typing is still painful. UR will work with UX to figure out how to manage. Anyone who wants to see raw video footage of the tests can contact Mary Trombley.

== '''Market Insights''' ==
=== Desktop / Platform ===
==== Apple ====
* Apple was granted [http://da.feedsportal.com/c/34438/f/628517/s/200bc187/l/0L0Spatentlyapple0N0Cpatently0Eapple0C20A120C0A60Capple0Ewins0Epatents0Efor0Eindustrial0Edesign0Efuture0E3d0Eremote0Eharnessing0Epower0Ethrough0Eelectromagnetic0Einduction0Bhtml/ia1.htm 22 patents] covering everything from industrial design to a futuristic 3D Apple TV remote and even a way that Apple envisions of harnessing power through electromagnetic induction to help extend battery life on iOS devices.
==== Microsoft ====
* The 6th Platform Preview for IE10 [http://blogs.msdn.com/b/ie/archive/2012/05/31/windows-release-preview-the-sixth-ie10-platform-preview.aspx now includes] the latest preview update for IE10. It includes an embedded Adobe Flash Player, which has been improved to support touch gestures. It is also integrated with the Process Lifetime Manager to better improve battery life in the Metro environment. Flash will also be bundled with the operating system and will receive improvements through Windows Update.
* The new release preview also sends a Do Not Track header by default, the first web browser to do so.
* IE10 now supports unprefixed versions of CSS transitions, transforms, animations, gradients, and CSS Fonts’ font-feature-settings property, as well as platform APIs such as the Indexed Database API (IndexedDB) and requestAnimationFrame().
* IE10 will also [http://blogs.msdn.com/b/ie/archive/2012/06/04/legacy-dx-filters-removed-from-ie10-release-preview.aspx no longer support] IE4's visual filters and transitions for anything other than intranet sites
* Interesting, Microsoft is going to great lengths to force adoption of the Metro-style interface, even to the point of [http://venturebeat.com/2012/05/31/windows-8-start-button-2 removing all code from Windows 8 referencing the Start button/menu] to prevent third-party developers from creating a workaround allowing people to continue using it
* Microsoft's Bing Mobile team released [https://www.onx.ms/#!findOutMorePage On-Ex], an Android application that is a sort of "if this then that" for mobile phones. Powered by Javascript, it offers some interesting API calls -- [https://www.onx.ms/#apiPage/modeOfTransport modeOfTransport] returns whether the user is walking, running or driving.
* Analysts are estimating that new Windows RT tablets will be in the [http://computerworld.co.nz/news.nsf/technology/windows-rt-tablets-could-cost-500-to-700 $500-$700 price range], which raises concerns for their viability

==== Google ====
* Fully hardware-accelerated CSS filters [http://blog.chromium.org/2012/06/accelerated-css-filters-landed-in.html are available in Chrome/Chromium version 19 and newer]
* The press are heralding the upcoming Chrome version 21 as being optimized for [http://www.geek.com/articles/geek-pick/google-chrome-21-gears-up-for-gaming-20120530/ web-based gaming]
==== Security ====
* [http://krebsonsecurity.com/2012/05/facebook-takes-aim-at-cross-browser-lilyjade-worm Facebook is trying to stop a browser plugin-based worm] that uses the Crossrider cross-platform plugin creation tool.
==== Tizen ====
* A Tizen developer ran the [http://www.tizenexperts.com/2012/05/tizen-lord-rings-ringmark-facebook/ RingMark test] on Tizen, Android, and iPhone smartphones. Tizen was the clear leader with 141 passed Ring 1 tests.
==== Gaming ====
* The authors of Scirra, an HTML5 gaming framework, [http://www.scirra.com/blog/85/the-great-html5-mobile-gaming-performance-comparison did an HTML5 desktop/mobile gaming shootout using 23 different combinations of browsers and devices]. Firefox got the highest score for desktop but the lowest for Android 4.0.

=== Mobile ===

Summary below, full update [http://irinasandu.com/2012/06/06/android-and-mobile-browsing-insights-week-23/ here] and in your inbox.

* Opera announced it reached 189.6 million mobile users, a new version of Opera Mini for basic phones and a partnership with America Movil and one with Bharti Airtel

* 65% of all Androids run Gingerbread, 19% Froyo and 7% Ice Cream Sandwich

* The hardware section of the Play Store expansing with accessories

* Researchers found security flaws in Google Bouncer

* HTC and Sony partnered to augment their mobile offerings

* First Android device on x86 architecture available in Europe

* Samsung Galaxy S III landing in market, Galaxy Note 2 rumoured to launch in October

* Asus, Acer and Toshiba to be among Windows 8 tablet manufacturers

* Video of Tizen on Samsung reference device [http://www.tizenexperts.com/2012/05/hands-tizen-developer-prototype-device/ available]

* By 2015 smartphones will account for 75% of new phones sold

== Marketing, Press & Public Reaction ==

==== Marketing ====

* Finalizing materials for releases later this week; getting started on the next round of releases.
* LMesa and GJimenez finishing handoff to LForrest; Will start in earnest next week.

==== Press ====

*[http://www.pcworld.com/businesscenter/article/256886/six_good_reasons_to_download_firefox_13.html Six Good Reasons to Download Firefox 13] 
*[http://www.webmonkey.com/2012/06/firefox-13-a-faster-smarter-web-browser/ Firefox 13: A Faster, Smarter Web Browser] 
*[http://www.webpronews.com/firefox-13-releases-a-day-before-official-launch-2012-06 Firefox 13 Releases A Day Before Official Launch] 
*[http://blogs.cio.com/browsers/17135/firefox-13-arrives-snazzy-features-rival-chrome Firefox 13 Arrives with Snazzy Features that Rival Chrome] 

 

== Questions, Comments, FYI ==
* If you see :gps, give him a giant hug, or a beer.

== Actions this week ==

Firefox/Channels/Meetings/2012-06-05

2012-06-05T21:17:26Z

Lmesa: /* Marketing/Communications */

Firefox/Channels/Meetings/2012-06-05

2012-06-05T21:03:52Z

Lmesa: /* Marketing/Communications */

Firefox/Planning/2012-06-06

2012-06-05T16:45:54Z

Lmesa: /* Marketing, Press & Public Reaction */

Engagement/Developer Engagement/BrowserIDPlan/Weekly Meetings

2012-06-05T16:24:43Z

Lmesa: /* Persona Dev Engagement Meeting Notes */

=== Persona Dev Engagement Meeting Notes ===
* [https://etherpad.mozilla.org/PersonaDevEngage-6-5-2012 6-5-2012]
* [https://etherpad.mozilla.org/PersonaDevEngage-5-29-2012 5-29-2012]
* [https://etherpad.mozilla.org/PersonaDevEngage-5-15-2012 5-15-2012]
* [https://etherpad.mozilla.org/PersonaDevEngage-5-8-2012 5-8-2012]
* [https://etherpad.mozilla.org/PersonaDevEngage-5-3-2012 5-3-2012]

Firefox/Channels/Meetings/2012-05-31

2012-05-31T21:08:31Z

Lmesa: /* Marketing/Communications */

Releases/Firefox 13/Final Signoffs

2012-05-30T18:48:22Z

Lmesa: /* Outstanding Issues/Concerns */

This page will track declaring the latest mozilla-beta build as the final in this cycle and starting the build off of the mozilla-release repository.

'''Please note that issues found in the final moments of the beta period may still require us to rebuild before release'''

== Focus Areas ==
=== Tracking Details ===
 

=== Add-ons ===
==== Current Status ====
 

==== Outstanding Issues/Concerns ====
 

=== Stability ===
==== Current Status ====
 

==== Outstanding Issues/Concerns ====
 

==== Mobile specific stability notes ====
 

=== QA ===
==== Current Status - Desktop ====
 

==== Outstanding Issues/Concerns - Desktop ====
 

==== Current Status - Mobile ====
 

==== Outstanding Issues/Concerns - Mobile ====
 

=== Security ===
==== Current Status ====
 

==== Outstanding Issues ====
 

=== Localization ===
==== Current Status ====
 

==== Outstanding Issues/Concerns ====
 

=== Build Mechanics ===
==== Current Status ====
 

==== Outstanding Issues/Concerns ====
 

=== Web Content ===
==== Current Status ====
* On track for 6/5
* Tracking bug: https://bugzilla.mozilla.org/show_bug.cgi?id=749733
* Biggest concern is Implementing the new WN page (https://bugzilla.mozilla.org/show_bug.cgi?id=752689) because of concern for localization of the page and SUMO links.
** Worst case, only show the page in en-US and use the template for other locales.
* Blog Posts need sign-off from PM this week. Will be sending email shortly.

==== Outstanding Issues/Concerns ====
* Release notes
** make sure we add/update system requirements to include the fact that we no longer support Win2K and Win XP (From what I can tell this was already done?)

=== Services ===
==== Current Status ====
 

==== Outstanding Issues/Concerns ====
 

=== ESR ===
==== Current Status - Desktop ====
 

==== Outstanding Issues/Concerns - Desktop ====
 

==== Current Status - Mobile ====
 

==== Outstanding Issues/Concerns - Mobile ====

Firefox/Planning/2012-05-30

2012-05-30T16:36:38Z

Lmesa: /* Marketing, Press & Public Reaction */

Releases/Firefox 13/Final Signoffs

2012-05-29T19:42:33Z

Lmesa: /* Web Content */

This page will track declaring the latest mozilla-beta build as the final in this cycle and starting the build off of the mozilla-release repository.

'''Please note that issues found in the final moments of the beta period may still require us to rebuild before release'''

== Focus Areas ==
=== Tracking Details ===
 

=== Add-ons ===
==== Current Status ====
 

==== Outstanding Issues/Concerns ====
 

=== Stability ===
==== Current Status ====
 

==== Outstanding Issues/Concerns ====
 

==== Mobile specific stability notes ====
 

=== QA ===
==== Current Status - Desktop ====
 

==== Outstanding Issues/Concerns - Desktop ====
 

==== Current Status - Mobile ====
 

==== Outstanding Issues/Concerns - Mobile ====
 

=== Security ===
==== Current Status ====
 

==== Outstanding Issues ====
 

=== Localization ===
==== Current Status ====
 

==== Outstanding Issues/Concerns ====
 

=== Build Mechanics ===
==== Current Status ====
 

==== Outstanding Issues/Concerns ====
 

=== Web Content ===
==== Current Status ====
* On track for 6/5
* Tracking bug: https://bugzilla.mozilla.org/show_bug.cgi?id=749733
* Biggest concern is Implementing the new WN page (https://bugzilla.mozilla.org/show_bug.cgi?id=752689) because of concern for localization of the page and SUMO links.
** Worst case, only show the page in en-US and use the template for other locales.
* Blog Posts need sign-off from PM this week. Will be sending email shortly.

==== Outstanding Issues/Concerns ====
* Release notes

=== Services ===
==== Current Status ====
 

==== Outstanding Issues/Concerns ====
 

=== ESR ===
==== Current Status - Desktop ====
 

==== Outstanding Issues/Concerns - Desktop ====
 

==== Current Status - Mobile ====
 

==== Outstanding Issues/Concerns - Mobile ====

Engagement/Developer Engagement/BrowserIDPlan/Weekly Meetings

2012-05-29T18:22:08Z

Lmesa: /* Persona Dev Engagement Meeting Notes */

=== Persona Dev Engagement Meeting Notes ===
* [https://etherpad.mozilla.org/PersonaDevEngage-5-29-2012 5-29-2012]
* [https://etherpad.mozilla.org/PersonaDevEngage-5-15-2012 5-15-2012]
* [https://etherpad.mozilla.org/PersonaDevEngage-5-8-2012 5-8-2012]
* [https://etherpad.mozilla.org/PersonaDevEngage-5-3-2012 5-3-2012]

Identity/persona.org

2012-05-18T16:02:57Z

Lmesa: /* Overview */

This page contains all of the important details for '''persona.org'''.

= Elevator Pitch =
persona.org is a portal for people to manage their online life (apps, contacts, identity). First step is an Apps launcher.

== Overview ==
* Prod URL: http://persona.org
* Dev URL: https://persona-dev.mozillalabs.com
* Stage URL: TBD
* Code Repo: https://github.com/mozilla/persona.org
* L10N Repo: TBD
* Code: node.js
* Product Owner: Ben Adida
* Product Marketing Manager: Laura Mesa (please notify before pushing anything live).
* Dev Team: Jen Fong, Sean McArthur
* IRC Channel: [irc://irc.mozilla.org:6697/persona.org #persona.org on irc.mozilla.org]

== Project Status ==
* Target release date: April 25, 2012 (Alpha)
* '''Status meetings:''' Thursdays, 12pm Pacific, Vidyo and in-person: Mountain View-2G (Gigo)
* Beta target release date: late July 2012

= Specs / Useful links =

* [https://etherpad.mozilla.org/uEt2c54rn7 Initial guidelines for node.js code style and setup]

= Bugs =
Bugs are tracked on github:

* [https://github.com/mozilla/persona.org/issues Github Issues for persona.org]

Identity/persona.org

2012-05-18T16:00:01Z

Lmesa: /* Elevator Pitch */

This page contains all of the important details for '''persona.org'''.

= Elevator Pitch =
persona.org is a portal for people to manage their online life (apps, contacts, identity). First step is an Apps launcher.

== Overview ==
* Prod URL: http://persona.org
* Dev URL: https://persona-dev.mozillalabs.com
* Stage URL: TBD
* Code Repo: https://github.com/mozilla/persona.org
* L10N Repo: TBD
* Code: node.js
* Product Owner: Ben Adida
* Product Marketing Manager: Laura Mesa
* Dev Team: Jen Fong, Sean McArthur
* IRC Channel: [irc://irc.mozilla.org:6697/persona.org #persona.org on irc.mozilla.org]

== Project Status ==
* Target release date: April 25, 2012 (Alpha)
* '''Status meetings:''' Thursdays, 12pm Pacific, Vidyo and in-person: Mountain View-2G (Gigo)
* Beta target release date: late July 2012

= Specs / Useful links =

* [https://etherpad.mozilla.org/uEt2c54rn7 Initial guidelines for node.js code style and setup]

= Bugs =
Bugs are tracked on github:

* [https://github.com/mozilla/persona.org/issues Github Issues for persona.org]

Firefox/Planning/2012-05-16

2012-05-16T18:04:56Z

Lmesa: /* Marketing, Press & Public Reaction */

<center>[[Firefox/Planning/{{#time: Y-m-d | {{SUBPAGENAME}} -1 week}}|« previous week]] | [[Firefox/DeliveryMeetings|index]] | [[Firefox/Planning/{{#time: Y-m-d | {{SUBPAGENAME}} +1 week}}|next week »]]</center>

'''Planning Meeting Details'''
* Wednesdays - 11:00am PDT, 18:00 UTC
* Mountain View Offices: Warp Core Conference Room
* Toronto Offices: Finch Conference Room
* [irc://irc.mozilla.org/planning irc.mozilla.org #planning] for backchannel
* (the [[Platform#Meetings|developer meeting]] takes place on Tuesdays)

'''Video/Teleconference Details - NEW'''
* 650-903-0800 or 650-215-1282 x92 Conf# '''95312''' (US/INTL)
* 1-800-707-2533 (pin 369) Conf# '''95312''' (US)
* Vidyo Room: Warp Core
* Vidyo [https://v.mozilla.com/flex.html?roomdirect.html&key=UK1zyrd7Vhym Guest URL]

{{Notes}}

__FORCETOC__

== Actions from Last Week ==

== Schedule & Progress on [[Releases|Upcoming Releases]] ==
=== Kilimanjaro ===

===Firefox Desktop ===
==== Release (12, 10esr, 3.6) ====
* Merge day may move one day earlier than ship date to decouple necessary work and meet our Aurora/Beta ship by the end of the week. See dev.planning thread.

==== Beta (13) ====
* FF13 beta 4 will be released on Friday

==== Aurora (14) ====

==== Nightly (15) ====
Bug 754133 - Set background of standalone images (the image itself, not the whole page) to white

=== Firefox Mobile ===
* [https://www.mozilla.org/en-US/mobile/14.0beta/releasenotes/ Fennec Native 14 beta 1] is now live on [https://play.google.com/store/apps/details?id=org.mozilla.firefox_beta Google Play]
* We expect our next beta of Fennec Native (released as early as 5/17) to be multi-locale with the same 13 localizations as XUL Fennec previously
*Day 1 Adoption
**Installs: 785,103 (+3.45% from yesterday)
**Active installs: 209,076 (+14.32%)
**Total Beta ADIs: 39,224 (+66.34%)
**ADIs on 14.0: 15,345 (39% of total ADIs)

=== Services ===
==== Firefox Sync ====
* Beta is out! \o/
* Please remember you can have only 1 native sync per android device, so no you cannot have Aurora & Beta syncing at the same time. [https://wiki.mozilla.org/User:Anaaktgeboren/NativeSync#Android_Sync_behavior_with_multiple_Firefox_versions_installed Read Why Here]

==== Apps In the Cloud Server ====
* Regular deployment happening.

=== Add-on SDK ===

Release (1.7 -> Firefox 12, 13)

* Released SDK 1.7 yesterday
** mixed bouquet of new features and important bug fixes
** css-only page-mods, l10n pluralization goodness
** configurable contentURL property for panel and widget!
** many bug fixes

Stabilization (1.8 -> Firefox 13, 14)

* on-track for release Tuesday June 26th
* first beta release either today or tomorrow?

Development (1.9 -> Firefox 14, 15)

* Firefox 15 / memory leak issues mitigated by latest khuey patch
** still planning to spin up a campaign to get older extensions re-packed, because its the right thing to do
** more plannig for this will happen at the Addons work week, June 4.

===Identity===

===Apps===
* Firefox Desktop 14 (Aurora) - landed
** Looking to back out this functionality - {{bug|750936}}
** Native Install
** Chromeless launch of apps

* Mozillian Marketplace Release is out! Thanks for the feedback so far!
** Please be mindful that this is an internal release and of alpha quality. Early access is limited to Mozillians and partners for testing, so please do not tweet, communicate or share screenshots, features or details about the Marketplace for now.
** Download Firefox Desktop Nightly (Fx15)
** Have a look at the [https://wiki.mozilla.org/Marketplace/Mozillian_Preview wiki] to learn more about the testing procedure.
** If you run into any hiccups, you can report them to apps-feedback@mozilla.com.
** Once you’re done, there’s also an [http://qsurvey.mozilla.com/s3/mozillianspreview online survey] for you to fill out.

* Firefox Desktop 15 (Nightly)
** Working on fixing bugs - mostly fit and polish to fit Kilimanjaro requirements

* Firefox Mobile 15 (Nightly) - in progress
** Work started in Fx14 continues in 15.
** Proposed marketplace bundling with Fennec is an open issue. See {{bug|738545}}

* Apps in the Cloud
** AITC client continues
** AITC Server - Completed

== Feedback Summary ==
=== Desktop ===
Firefox 12 issues summary:

We currently have a 5% increase in issues over Firefox 11. This seems to be a combination of issues including:

Firefox 12 is slow - Thread was originally about a gfx card issue, but I think it turned into a pile on thread https://support.mozilla.org/en-US/questions/926621
[http://input.mozilla.org/en-US/opinion/2931234]
[http://input.mozilla.org/en-US/opinion/2930930]

Foxit Reader causing Hotmail issues: Solution is to rollback to an older version of Foxit. This combined with the Adobe Reader issue is sticky.
[https://support.mozilla.org/en-US/questions/739403]
https://support.mozilla.org/en-US/questions/926740
[http://input.mozilla.org/en-US/opinion/2929657]
[http://input.mozilla.org/en-US/opinion/2928595]

PDF Issues on Mac - Reader update https://support.mozilla.org/en-US/questions/775819
[https://support.mozilla.org/en-US/questions/926799]
[http://input.mozilla.org/en-US/opinion/2930373]
[http://input.mozilla.org/en-US/opinion/2925866]

Firefox 12 consumes too much memory - https://support.mozilla.org/en-US/questions/927004
[http://input.mozilla.org/en-US/opinion/2931561]
[http://input.mozilla.org/en-US/opinion/2930795]
[http://input.mozilla.org/en-US/opinion/2929091]

Copy/Paste Image - Fixed - https://bugzilla.mozilla.org/show_bug.cgi?id=749527
[http://input.mozilla.org/en-US/opinion/2926818]
[http://input.mozilla.org/en-US/?product=firefox&version=12.0&date_start=2012-04-24&date_end=2012-05-16&q=copy+image]

Firefox 12 incorrectly caching pages - Bug filed - https://bugzilla.mozilla.org/show_bug.cgi?id=748647
[https://support.mozilla.org/en-US/questions/926043]

Incompatible Norton Toolbar: Need to update norton 360 and norton internet security suite.
[https://support.mozilla.org/en-US/questions/925899]
[http://input.mozilla.org/en-US/?q=norton&product=firefox&version=12.0&sentiment=sad&date_start=2012-04-07]

FF12 praise summary, down 6% from FF11:

fast:
[http://input.mozilla.org/en-US/opinion/2931689]
[http://input.mozilla.org/en-US/opinion/2931687]
[http://input.mozilla.org/en-US/opinion/2931430]

ui:
[http://input.mozilla.org/en-US/opinion/2930426]
[http://input.mozilla.org/en-US/opinion/2929294]

stable:
[http://input.mozilla.org/en-US/opinion/2924997]
[http://input.mozilla.org/en-US/opinion/2894948]
[http://input.mozilla.org/en-US/opinion/2891593]

=== Mobile ===

== UX & User Research ==
=== UX Design ===

* [apps integration] [http://cl.ly/3X2E2g0n0M1X0P0g2I3R awesomebar/apps integration concept sketching] (Madhava)
* [android] Collating beta1 UX feedback [https://etherpad.mozilla.org/betaUXfeedback etherpad here] (Madhava)
* [android] Finishing tab menu designs for next version; finalizing designs for search suggest; widget; custom menu (Ian)
* [metro] Incorporating feedback from last video sketch; preparing another one around interactions of basic browser usage (yuan)
* [B2G Firefox] (Larissa)
** [http://people.mozilla.com/~lco/FX_B2G/Release_1_Specs/R1_Tabs_v1.pdf v1 tabs interaction spec]
** revising start page spec; starting on details of sharing and browser settings
* [sign-into-browser / ID integration] (Zhenshuo)
** [http://people.mozilla.com/~zfang/PersonaID/Australis-SignInToSites.jpg sign into '''sites''' exploration]
* [desktop] [https://etherpad.mozilla.org/Preferences more ideas for preferences simplification] (Zhenshuo)

== '''Market Insights''' ==
=== Desktop / Platform ===
==== Adobe ====
* After initially requiring users to pay hundreds of dollars to receive security fixes for vulnerabilities in Flash Professional, Illustrator, and other products, Adobe has [http://www.computerworld.com/s/article/9227119/Adobe_backpedals_will_now_patch_software_for_free relented] and will now provide them for free
==== Apple ====
* A fairly significant [http://www.tuaw.com/2012/03/22/security-alert-safari-for-ios-5-1-reportedly-vulnerable-to-addr/ security issue] was found in Safari's handling of input in the URL bar; a fix is expected shortly
==== Google ====
* Code recently [http://codereview.chromium.org/10392084/ landed] that integrates all of a users' Google Web History with their Chrome browsing history
* Google posted a [http://blog.chromium.org/2012/05/connect-with-web-intents.html web developer introduction, with video] to its Web Intents implementation
* [http://chrome.blogspot.ca/2012/05/keeping-tabs-on-your-tabs.html Tab syncing across devices] has now landed in the Chrome stable channel.
* The default extensions for Chrome have been updated to include [http://src.chromium.org/viewvc/chrome?view=rev&revision=135906 Google Docs]
==== Microsoft ====
* Microsoft posted a [http://blogs.msdn.com/b/ie/archive/2012/05/14/sharing-links-from-ie10-on-windows-8.aspx detailed summary, with video] of how social sharing of links and other content from IE10 will work on Windows 8.
* Senate Judiciary Committee staffers plan to take a look at allegations that Microsoft has made it difficult for competing Web browsers to run on a certain version of Windows, an aide told a [http://www.computerworld.com/s/article/9227121/Senate_to_look_at_Mozilla_s_browser_competition_allegations political blog]
* A leaked version of the [http://windows8beta.com/2012/05/leaks-of-windows-8-pre-release-preview-build-shows-improved-results-for-ie10-benchmarks upcoming Preview Release] of IE10 shows an improved score on html5test.com
==== Opera ====
* There are [http://www.favbrowser.com/is-opera-metro-for-windows-8-in-development-windows-phone-8-version-planned/ rumours] that Opera will be porting its Opera Mobile browser to the upcoming Windows Phone platform
* Opera Mini was also released for the [http://my.opera.com/chooseopera/blog/2012/05/09/opera-mini-for-bada Samsung Bada] platform
==== WebKit ====
* CSS Variables are [https://lists.webkit.org/pipermail/webkit-dev/2012-May/020633.html coming] to WebKit
* The tab-size property is now supported, and work has begun on the Media Capture API

=== Mobile ===

Summary below, full update [http://irinasandu.com/2012/05/16/android-and-mobile-browsing-insights-week-20/ here] and in your inbox.

* Updated Android version distribution numbers are available
* Google's Motorola acquisition expected to be completed soon
* Android 5.0, code-named Jelly Bean, rumoured to be released in fall with multiple flagship devices
* Baidu to be releasing Yi-based devices
* 56.1% of smartphone shipments in Q1 featured Android
* Samsung confirmed as top mobile phone vendor by shipments in Q1

== Marketing, Press & Public Reaction ==

==== Marketing ====
* Transition: Laura Forrest will be the new PMM for Desktop, with full transition by 6/18. Desktop is in excellent hands!
** In the meantime, Laura Mesa and Grace will continue leading through the next Desktop updates, including Aurora & Beta.
** Working through how this may/may not effect Beta and Aurora outbound.
* Otherwise, materials and blog posts on schedule for next update.

==== Press ====

[http://www.webmonkey.com/2012/05/firefox-for-android-preps-for-prime-time/ Firefox for Android Preps for Prime Time] 

[http://www.fiercemobilecontent.com/story/mozilla-updates-firefox-android-adobe-flash-support/2012-05-16 Mozilla updates Firefox for Android with Adobe Flash support] 

[http://www.h-online.com/open/news/item/Firefox-14-beta-for-Android-released-1577315.html Firefox 14 beta for Android released] 

[http://cnettv.cnet.com/hands-mozilla-firefox-os-boot-gecko/9742-1_53-50124428.html Hands on with Mozilla Firefox OS Boot to Gecko][http://www.internetnews.com/blog/skerner/google-chrome-19-syncs-your-life.-didnt-firefox-do-that-last-year.html]

== Questions, Comments, FYI ==

== Actions this week ==

Firefox/Channels/Meetings/2012-05-15

2012-05-15T21:12:37Z

Lmesa: /* Marketing/Communications */

<center>[[Firefox/Channels/Meetings/{{#time: Y-m-d | {{SUBPAGENAME}} -1 week}}|« previous week]] | [[Firefox/Channels/Meetings |index]] | [[Firefox/Channels/Meetings/{{#time: Y-m-d | {{SUBPAGENAME}} +1 week}}|next week »]]</center>

'''Channel Meeting Details'''
* Tuesdays and Thursday - 2:00pm PDT, 21:00 UTC
* Mountain View Offices: Warp Core Conference Room
* [irc://irc.mozilla.org/planning irc.mozilla.org #planning] for backchannel

'''Video/Teleconference Details - NEW'''
* 650-903-0800 or 650-215-1282 x92 Conf# '''95312''' (US/INTL)
* 1-800-707-2533 (pin 369) Conf# '''95312''' (US)
* Vidyo Room: Warp Core
* Vidyo [https://v.mozilla.com/flex.html?roomdirect.html&key=UK1zyrd7Vhym Guest URL]

{{Notes}}

__FORCETOC__

== Previous Actions ==
* <strike>Alex to follow up on the Hotmail regression {{bug|736731}}</strike>
* <strike>Alex to speak with Kev re: Silverlight crash {{bug|753248}}</strike>
* Michelle to file bug on Input for rapid betas build IDs {{bug|754050}}

== Schedule Update ==
* [https://www.mozilla.org/en-US/mobile/14.0beta/releasenotes/ Fennec Native 14 beta 1] is now live on [https://play.google.com/store/apps/details?id=org.mozilla.firefox_beta Google Play]!
** Bugs filed by following the link on the product page will have [Play] in the whiteboard
** Fennec Native betas will have a weekly cadence after this week as with desktop, going to build no later than Wednesday for a Friday push
** We expect our next beta of Fennec Native to be multi-locale with the same 13 localizations as XUL Fennec previously

* We're now [https://mail.mozilla.com/home/akeybl@mozilla.com/Release%20Management.html?view=month&date=20120515 here] in the schedule
* FF13 beta 4 will go-to-build today (5/15). We've asked engineering to continue working on [https://bugzilla.mozilla.org/buglist.cgi?field0-3-0=cf_status_firefox13;type0-1-0=notequals;value0-4-0=verified;field0-1-0=cf_status_firefox13;field0-0-0=cf_tracking_firefox13;type0-4-0=notequals;value0-3-0=unaffected;query_format=advanced;value0-2-0=fixed;value0-1-0=wontfix;type0-3-0=notequals;field0-2-0=cf_status_firefox13;field0-4-0=cf_status_firefox13;type0-0-0=equals;value0-0-0=%2B;type0-2-0=notequals;list_id=3088165 tracked bugs], looking for the lowest risk mitigating fix for remaining tracked bugs

* The next 3.6 EOL checkpoint is 5/28 when we push out the last round of MUs (one more auto-update round still to follow)

==Add-ons==
* {{bug|754723}} – Consider blocklisting Flash versions

== Stability ==

===Overall concerns===
* [http://bit.ly/vO7SxB Top crashes]
* List of top crashers increasing.
* Seem to be many issues that just get deferred because we can't find STR or don't understand the problem.
* Lots of new signatures over the last 4-6 mos, nothing happening.
* Need a formal strategy to get some of these worked.

* RelMan's recommendation would be:
** Go through each top crasher, read through crash comments, pull new correlation reports, update its status, and provide any leads for QA
** Ask the QA community to try to find STR for each top crasher, with rewards if found (t-shirt/bounty?)
** Automatically track all reproducible top crashers found for a future release and drive them as if they're a new regression
** Remaining top crasher bugs would then be blocked on a bug that would collect the necessary debug info to diagnose

===Aurora===
* [http://bit.ly/K2EmSe Crashes tracking Fx14]
* A couple of problems with AMD graphics cards {{bug|714320}} and {{bug|700288}} that we haven't been able to fix.
* {{bug|736695}} - nsGenericElement::UnbindFromTree , when I open Customize Toolbar with Video DownloadHelper 4.9.8 installed. A problem for a while.
* {{bug|753248}} - startup crash - silverlight issue on Mac 10.7.

===Beta===
* {{bug|704125}} - spike in crashes for banco de brazil.

===Release===
* In preparation for 10.8, we're now watching for [https://crash-analysis.mozilla.com/chofmann/20120514/top-mac-crashes-all.txt Mountain Lion top crashers]
* {{bug|640904}} - JSAutoEnterCompartment::enter. #2 crash on Fx12 with over 62K crashes in a 7 day period. Waiting for new version of add-on to get updated on AMO - need to escalate this.
* {{bug|572011}} - Crash @ nsDiskCacheStreamIO::FlushBufferToFile - been around for a while and no progress
* {{bug|597260}} - nsFileOutputStream::Write(char const*, unsigned int, unsigned int*) - another networking issue that has been around for while without progress.
* {{bug|597260}} - nsFileOutputStream::Write(char const*, unsigned int, unsigned int*). Another top 10 issue that doesn't make progress.

== QA ==
===Aurora===
 
===Beta===
[http://bit.ly/IhfxAz QAWANTED Bugs]
* Nothing in particular to discuss (ie. QA is not currently blocked on testing anything)

== RelEng ==
* win8
* win32-on-win64
* osx10.8 signing

== Marketing/Communications ==
* Handing off Desktop to Laura Forrest, with official hand-off date being 6/18.
** Unclear how this affects Aurora & Beta ownership
** Laura M and Grace will continue to own Desktop through Fx 13 launch, with Laura F taking on more and more as the weeks go by.
*** questions: send to pmm@mozilla.com
* Haven't gotten a naming agreement yet for new betas. Will have for sure for Thursday.
 

== Support ==
 

== Roundtable ==
* Rapid Betas - any lingering questions?
** (ashughes) - not a question, but I emailed around a proposal for QA automation:
*** limit locales to en-US + 1 random per platform
*** limit add-on pool to top-50
*** use add-on bucketing of top-10 + 10 random
*** should reduce execution time to ~4 hours
*** Q) Is that still too long? Is there too much risk involved in those reductions?
* Marcia plans to have a full QA test plan for Mountain Lion soon
* We're pursuing multiple avenues for how to handle the lack of Russian users on Beta, and specifically our difficulty with reproducing Yandex Toolbar issues
** Kev will be doing outreach to Yandex devs suggesting they move away from binary components, and we'll offer code inspection to make more stability suggestions
** We're also trying to get a Russian QA contact to help reproduce crashes, and considering sending out a CTA for Russian QA testers
* Investigating decoupling Merge from Release Day: https://etherpad.mozilla.org/merge-day
* What can we do about these [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=722312%2C700288%2C714320%2C745515%2C;list_id=3089183 Radeon top crashers]?
* [https://bugzilla.mozilla.org/buglist.cgi?type0-1-0=nowordssubstr;list_id=3088568;field0-1-0=cf_tracking_firefox14;field0-0-0=cf_blocking_fennec10;query_format=advanced;value0-1-0=fixed%20verified;type0-0-0=equals;value0-0-0=betaN%2B betaN+] blocking bugs for FN14b2
* Pulling release from Android store

== Actions ==
 
== Triage ==
=== Aurora Queries ===
* [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=ALL+flag%3Aapproval-mozilla-aurora%3F&order=Bug+Number '''Approval requests''']
* [https://bugzilla.mozilla.org/buglist.cgi?field0-0-0=cf_tracking_firefox{{AURORA_VERSION}}&resolution=---&resolution=DUPLICATE&query_format=advanced&type0-0-0=equals&value0-0-0=%3F&order=Bug%20Number&list_id=1793640 '''Tracking noms''']
* [https://bugzilla.mozilla.org/buglist.cgi?field1-0-0=cf_status_firefox{{AURORA_VERSION}};type0-0-0=equals;value0-0-0=%2B;field0-0-0=cf_tracking_firefox{{AURORA_VERSION}};type1-0-0=notregexp;value1-0-0=%28fixed|wontfix|unaffected|verified%29;order=Bug%20Number '''Unresolved Tracking Bugs for FF{{AURORA_VERSION}}''']

=== Beta Queries ===
* [https://bugzilla.mozilla.org/buglist.cgi?&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=approval-mozilla-beta%3F&order=Bug%20Number '''Approval requests''']
* [https://bugzilla.mozilla.org/buglist.cgi?&field0-0-0=cf_tracking_firefox{{BETA_VERSION}}&type0-0-0=equals&value0-0-0=%3F&order=Bug%20Number '''Tracking noms''']
* [https://bugzilla.mozilla.org/buglist.cgi?field1-0-0=cf_status_firefox{{BETA_VERSION}};type0-0-0=equals;value0-0-0=%2B;field0-0-0=cf_tracking_firefox{{BETA_VERSION}};type1-0-0=notregexp;value1-0-0=%28fixed|wontfix|unaffected|verified%29;order=Bug%20Number '''Unresolved Tracking Bugs for FF{{BETA_VERSION}}''']

Firefox/Channels/Meetings/2012-05-15

2012-05-15T21:11:26Z

Lmesa: /* Marketing/Communications */

<center>[[Firefox/Channels/Meetings/{{#time: Y-m-d | {{SUBPAGENAME}} -1 week}}|« previous week]] | [[Firefox/Channels/Meetings |index]] | [[Firefox/Channels/Meetings/{{#time: Y-m-d | {{SUBPAGENAME}} +1 week}}|next week »]]</center>

'''Channel Meeting Details'''
* Tuesdays and Thursday - 2:00pm PDT, 21:00 UTC
* Mountain View Offices: Warp Core Conference Room
* [irc://irc.mozilla.org/planning irc.mozilla.org #planning] for backchannel

'''Video/Teleconference Details - NEW'''
* 650-903-0800 or 650-215-1282 x92 Conf# '''95312''' (US/INTL)
* 1-800-707-2533 (pin 369) Conf# '''95312''' (US)
* Vidyo Room: Warp Core
* Vidyo [https://v.mozilla.com/flex.html?roomdirect.html&key=UK1zyrd7Vhym Guest URL]

{{Notes}}

__FORCETOC__

== Previous Actions ==
* <strike>Alex to follow up on the Hotmail regression {{bug|736731}}</strike>
* <strike>Alex to speak with Kev re: Silverlight crash {{bug|753248}}</strike>
* Michelle to file bug on Input for rapid betas build IDs {{bug|754050}}

== Schedule Update ==
* [https://www.mozilla.org/en-US/mobile/14.0beta/releasenotes/ Fennec Native 14 beta 1] is now live on [https://play.google.com/store/apps/details?id=org.mozilla.firefox_beta Google Play]!
** Bugs filed by following the link on the product page will have [Play] in the whiteboard
** Fennec Native betas will have a weekly cadence after this week as with desktop, going to build no later than Wednesday for a Friday push
** We expect our next beta of Fennec Native to be multi-locale with the same 13 localizations as XUL Fennec previously

* We're now [https://mail.mozilla.com/home/akeybl@mozilla.com/Release%20Management.html?view=month&date=20120515 here] in the schedule
* FF13 beta 4 will go-to-build today (5/15). We've asked engineering to continue working on [https://bugzilla.mozilla.org/buglist.cgi?field0-3-0=cf_status_firefox13;type0-1-0=notequals;value0-4-0=verified;field0-1-0=cf_status_firefox13;field0-0-0=cf_tracking_firefox13;type0-4-0=notequals;value0-3-0=unaffected;query_format=advanced;value0-2-0=fixed;value0-1-0=wontfix;type0-3-0=notequals;field0-2-0=cf_status_firefox13;field0-4-0=cf_status_firefox13;type0-0-0=equals;value0-0-0=%2B;type0-2-0=notequals;list_id=3088165 tracked bugs], looking for the lowest risk mitigating fix for remaining tracked bugs

* The next 3.6 EOL checkpoint is 5/28 when we push out the last round of MUs (one more auto-update round still to follow)

==Add-ons==
* {{bug|754723}} – Consider blocklisting Flash versions

== Stability ==

===Overall concerns===
* [http://bit.ly/vO7SxB Top crashes]
* List of top crashers increasing.
* Seem to be many issues that just get deferred because we can't find STR or don't understand the problem.
* Lots of new signatures over the last 4-6 mos, nothing happening.
* Need a formal strategy to get some of these worked.

* RelMan's recommendation would be:
** Go through each top crasher, read through crash comments, pull new correlation reports, update its status, and provide any leads for QA
** Ask the QA community to try to find STR for each top crasher, with rewards if found (t-shirt/bounty?)
** Automatically track all reproducible top crashers found for a future release and drive them as if they're a new regression
** Remaining top crasher bugs would then be blocked on a bug that would collect the necessary debug info to diagnose

===Aurora===
* [http://bit.ly/K2EmSe Crashes tracking Fx14]
* A couple of problems with AMD graphics cards {{bug|714320}} and {{bug|700288}} that we haven't been able to fix.
* {{bug|736695}} - nsGenericElement::UnbindFromTree , when I open Customize Toolbar with Video DownloadHelper 4.9.8 installed. A problem for a while.
* {{bug|753248}} - startup crash - silverlight issue on Mac 10.7.

===Beta===
* {{bug|704125}} - spike in crashes for banco de brazil.

===Release===
* In preparation for 10.8, we're now watching for [https://crash-analysis.mozilla.com/chofmann/20120514/top-mac-crashes-all.txt Mountain Lion top crashers]
* {{bug|640904}} - JSAutoEnterCompartment::enter. #2 crash on Fx12 with over 62K crashes in a 7 day period. Waiting for new version of add-on to get updated on AMO - need to escalate this.
* {{bug|572011}} - Crash @ nsDiskCacheStreamIO::FlushBufferToFile - been around for a while and no progress
* {{bug|597260}} - nsFileOutputStream::Write(char const*, unsigned int, unsigned int*) - another networking issue that has been around for while without progress.
* {{bug|597260}} - nsFileOutputStream::Write(char const*, unsigned int, unsigned int*). Another top 10 issue that doesn't make progress.

== QA ==
===Aurora===
 
===Beta===
[http://bit.ly/IhfxAz QAWANTED Bugs]
* Nothing in particular to discuss (ie. QA is not currently blocked on testing anything)

== RelEng ==
* win8
* win32-on-win64
* osx10.8 signing

== Marketing/Communications ==
* Handing off Desktop to Laura Forrest, with official hand-off date being 6/18.
** Unclear how this affects Aurora & Beta ownership
** Laura M and Grace will continue to own Desktop through Fx 13 launch, with Laura F taking on more and more as the weeks go by.
*** questions: send to pmm@mozilla.com
 

== Support ==
 

== Roundtable ==
* Rapid Betas - any lingering questions?
** (ashughes) - not a question, but I emailed around a proposal for QA automation:
*** limit locales to en-US + 1 random per platform
*** limit add-on pool to top-50
*** use add-on bucketing of top-10 + 10 random
*** should reduce execution time to ~4 hours
*** Q) Is that still too long? Is there too much risk involved in those reductions?
* Marcia plans to have a full QA test plan for Mountain Lion soon
* We're pursuing multiple avenues for how to handle the lack of Russian users on Beta, and specifically our difficulty with reproducing Yandex Toolbar issues
** Kev will be doing outreach to Yandex devs suggesting they move away from binary components, and we'll offer code inspection to make more stability suggestions
** We're also trying to get a Russian QA contact to help reproduce crashes, and considering sending out a CTA for Russian QA testers
* Investigating decoupling Merge from Release Day: https://etherpad.mozilla.org/merge-day
* What can we do about these [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=722312%2C700288%2C714320%2C745515%2C;list_id=3089183 Radeon top crashers]?
* [https://bugzilla.mozilla.org/buglist.cgi?type0-1-0=nowordssubstr;list_id=3088568;field0-1-0=cf_tracking_firefox14;field0-0-0=cf_blocking_fennec10;query_format=advanced;value0-1-0=fixed%20verified;type0-0-0=equals;value0-0-0=betaN%2B betaN+] blocking bugs for FN14b2
* Pulling release from Android store

== Actions ==
 
== Triage ==
=== Aurora Queries ===
* [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=ALL+flag%3Aapproval-mozilla-aurora%3F&order=Bug+Number '''Approval requests''']
* [https://bugzilla.mozilla.org/buglist.cgi?field0-0-0=cf_tracking_firefox{{AURORA_VERSION}}&resolution=---&resolution=DUPLICATE&query_format=advanced&type0-0-0=equals&value0-0-0=%3F&order=Bug%20Number&list_id=1793640 '''Tracking noms''']
* [https://bugzilla.mozilla.org/buglist.cgi?field1-0-0=cf_status_firefox{{AURORA_VERSION}};type0-0-0=equals;value0-0-0=%2B;field0-0-0=cf_tracking_firefox{{AURORA_VERSION}};type1-0-0=notregexp;value1-0-0=%28fixed|wontfix|unaffected|verified%29;order=Bug%20Number '''Unresolved Tracking Bugs for FF{{AURORA_VERSION}}''']

=== Beta Queries ===
* [https://bugzilla.mozilla.org/buglist.cgi?&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=approval-mozilla-beta%3F&order=Bug%20Number '''Approval requests''']
* [https://bugzilla.mozilla.org/buglist.cgi?&field0-0-0=cf_tracking_firefox{{BETA_VERSION}}&type0-0-0=equals&value0-0-0=%3F&order=Bug%20Number '''Tracking noms''']
* [https://bugzilla.mozilla.org/buglist.cgi?field1-0-0=cf_status_firefox{{BETA_VERSION}};type0-0-0=equals;value0-0-0=%2B;field0-0-0=cf_tracking_firefox{{BETA_VERSION}};type1-0-0=notregexp;value1-0-0=%28fixed|wontfix|unaffected|verified%29;order=Bug%20Number '''Unresolved Tracking Bugs for FF{{BETA_VERSION}}''']

Release Management/Rapid Betas

2012-05-10T22:15:33Z

Lmesa: /* Blockers */

= Benefits of Rapid Betas =
* shorter verification turn-around time
* freed up RelEng/QA resources
* late-breaking beta issues can be much more easily resolved
* more user testing over the 6 week cycle
= Proposed Timeline =
* -4/23
** Consider major pain points, begin scoping work.
* 4/24-6/4
** Complete scoping work, begin implementation
** Communicate the plan to Mozilla community
** Move to Tuesday go, Wednesday ship? (see QA questions below)
** Any necessary in-product changes should land while FF15 is on m-c
* 6/5-7/16
** Complete implementation, begin process testing on Nightly/Aurora
* Week of 7/17
** Push out our first rapid beta while FF15 on mozilla-beta
= In-Product =
== Questions ==
* What do we do about non-admin users? What's the current experience? Can we back off on offering them an update by 7 days?
** should be possible be possible by only incrementing the update xml's appVersion attribute once a week see {{bug|753103}}
* Will the user be prompted at all to "apply the update now"? Can we disable that?
* If the user's browser downloads an update, then the user doesn't close and open their browser for 3 days, what build will be applied?
* Is the user going to be prompted every day to update, or will it be truely silent and the user won't notice it until the next day.
* Will our current beta users be happy with the additional bandwidth of potentially downloading updates every day?

== Blockers ==
* [https://wiki.mozilla.org/Background_Updates Background updates] will be landing in FF15.
** [[Silent_Update_updater | Feature page]]
** Tracking {{bug|307181}}, {{bug|753103}}

=Automation=
== Questions ==
* What are the communication points that need to happen (what needs to be communicated and when between the QA & RelEng)
* What can we do to keep automation running as smoothly as possible with known/unknown failures or automation glitches? ie: we will still need troubleshooting from QA when automation cuts out due to errors
== Blockers ==

= QA =
== Questions ==
* breakdown of when sign off has uncovered new regressions in a beta? (and if it has, was it through automation or manual (human) tests?)
** If we find that sign-off has not found new critical beta regressions, can we start shipping betas on Wednesdays after automated testing runs through (prior to rapid betas being implemented)? Bug verification, exploratory testing, and other smoke tests could continue out-of-band.
* can automating the release test plan be done against nightly/aurora in preparation for moving to faster beta releases?
* Can we automate mobile update testing? If so, we can even make the weekly push to the Play Store automatic.
== Blockers ==
* Update testing (and smoke tests) should be automated and worked into the build/push flow

=Support=
== Questions ==
* any pain points in supporting Aurora? (expand those into to-do items for supporting rapid betas)
== Blockers ==
= RelEng/IT =
== Questions ==
* any issues with automated pushsnip to beta channel?
** Needs to be gated on QA. We already automatically push to betatest. [[User:Catlee|Catlee]] 12:48, 13 April 2012 (PDT)
* can we add inputs from QA to incorporate the sign-off as part of automation?
* any possible issues with load (or mirrors) if we move to more frequent releases of beta on bouncer?
* Using the signing key appears to be a manual process currently, can this be automated?
** Already is! (except for android) - [[User:Catlee|Catlee]] 12:39, 13 April 2012 (PDT)
** note: upcoming osx10.8 signing is explicitly excluded
* Can we do the work associated with rapid betas be done in such a way that we could move back to weekly betas in the case of unforseen problems?
* Do we need to tag/package source for rapid betas?

== Blockers ==
* Tracking bug for RelEng work is {{bug|747168}}. Most notable items on it are:
** Automate android signing {{bug|705807}}
** Move master-side logic to client-side scripts: {{bug|748773}}, {{bug|748794}}, {{bug|748796}}, {{bug|748798}}, {{bug|748800}}
** Make mail notification work without a reconfig {{bug|749587}}
** Automate snippet optimization {{bug|748801}}
** Switch to using a different L10n url to get changesets for desktop: {{bug|751703}}, and keep the changeset info from each build in the manifest (to be created by releng as a replacement for tagging)

* unrelated but blocker: supporting new OS/platforms.

= Crash-Kill Team & Soccorro =
== Questions ==
* What are the implications of switching to rapid betas? How would crash analysis be different than m-c or m-a?
* Do we need to implement windowing over multiple build IDs to emulate having a large beta population on a single beta?
* What is a unit of 'enough' user testing data (days?) for getting feedback on a regression fix?
== Blockers ==
* Scoping happening [https://wiki.mozilla.org/Socorro:Rapid_Betas here]
* Tracking {{bug|752956}}
* [https://wiki.mozilla.org/Socorro:Rapid_Betas:Requirements Requirements]
* [https://wiki.mozilla.org/Socorro:Rapid_Betas:Implementation_Plan Implementation Plan]

= L10N =
== Answers/Resolutions ==
* Keep sign-offs on release and beta channel, continue without signoffs on aurora and central
* Drop the use of milestones at least for rapid betas
* Get l10n-changesets from urls that give the current signed-off state for a product/version
** These urls need to updated on migration day every six weeks
** These urls are already existing, using the av= keyword argument with the right code instead of a ms= keyword
== Questions ==
* What do we do with l10n milestones?
* Could we work towards automatically pulling from a beta branch? This doesn't really scale well.
* Could l10n_changesets be dynamically created from the csets on beta branch for locales in shipped_locales?
* Can l10n sign offs be automated? Test suites that check for anything other than string changes?

New questions:
* What happens with non-rapid betas, notably TB/SeaMonkey? '''(No change, continue as usual)'''
* Do we need a "sealed" status for release, or is that good to go without milestones, too? '''(That is up to the needs of the l10n drivers, do you want a tagged repo every 6 weeks when a release goes out?)'''

== Blockers ==
* None, but a releng bug on using the new url: {{bug|751703}}

= Release Management =
'''Update''' - RelEng (and lsblakk) met and discussed the complete process of releasing betas and have scoped the work involved in meeting this project's goals [https://wiki.mozilla.org/ReleaseEngineering/Rapid_Release_Nightly_Betas#Live_Notes here]
== Questions ==
* What should we call beta nightlies (Rapid Betas)?
* How do we communicate beta nightlies?
* The beta release process is a useful tool for verifying the final release process. If we change the final release process, how will we verify the changes or bring new people up to speed without affecting the timing of the final releases?
** Do we need to build in a slightly larger window for the final release to allow for these types of issues?
== Blockers ==
* Need to change the process of approving for Beta to first go through Aurora, for sake of risk mitigation
* We need to watch for more stretch across multiple versions of beta than we currently have across weekly betas
* Feature request: getting BuildIDs in Input to get more data on where feedback is coming from
* What's new page - either always on or always off but we'll need a better plan

= Metrics =
We did a sample analysis on the crash report data for beta for last 10 days of april.
The 9 out of the top 10 crashers in the 1st hour remain in the top 10 of the last hour of the 10 day period.
We probably will not be able to pick up enough reports to catch the rare crashes on day 1, so these will persist in subsequent builds and will be picked up later.

In summary:
- Using Rapid Builds we will be able to push bug fixes faster.
- Rare signatures will be picked up later (once enough reports come in) and in this regard Rapid Builds is not much different from weekly builds.

= Product Marketing & PR =
'''Update''' - Grace & Laura discussed; EJ added input; Laura discussed in channel meeting, wrote down answers.
== Questions & Responses ==
* This will have an impact on how we could deploy a What's New Page which we've planning to do for sometime. We will likely still be able to, but we'll have to coordinate much closer on when and how those pages are turned off and on. What would be the details of getting a paged turned on or off?
** No clear answer on this. This is not a blocker, but something to keep in mind for the future to find a solution.
* How will this effect release notes? Will we update them every day? Once a week?
** Will keep doing release notes the way we do Aurora--stand them up with initial release and make minor changes as needed; don't think we will see major changes between first release and end of the cycle.
* How will this effect how we track comments/feedback on Input?
** Yes, it will. Will need a way to correlate comments to buildIDs.
* Will this effect how we track ADUs/ADIs with metrics tools?
** Yes, Alex is filing a bug.
* How will users be alerted to the updates? Will it cause update fatigue?
** No because this will only be implemented after silent updates.
* Is this the new way of doing things or a short term thing we are testing?
** Its the plan for the foreseeable future, but may be changed depending on resources, needs, etc.
* Does this mean new features can land in beta?
** It makes it less risky to land features, but any feature additions will be discussed in depth before landing; don't think this will cause an increase in the landing of new features.
* Do we have to update our communications around what to expect for each channel?
** I don't think it does, apart from a general blog post announcing the change.
* Will this change the release timeline?
** No, this shouldn't effect release timeline at all.

== Blockers & Answers ==
* Blog Post communicating change on FoF; must be reviewed by PMMs and PR
** This will be done in conjunction with Alex Keybl, Mark Lavine/EJ and LMesa; timing tbd.
* Alignment on naming (we don't see a reason to change the name and didn't like adding "rapid" to releases)
** Grace, LMesa and EJ to discuss and come back with proposals
*** continuous betas?
*** rolling betas?
*** seamless betas?
* Figuring out how to make release notes work for all audiences/communications
** Don't think this will be a huge concern; see above.
* This will impact if/when/how often we want to communicate about betas
** This is unlikely as the changes that will be done between betas will probably stay with bug fixes, security fixes or feature back outs.
* Updating all channel comms
** Unlikely outside of blog post mentioned above. Ej/LM/ML to discuss.

Release Management/Rapid Betas

2012-05-10T22:09:26Z

Lmesa: /* Product Marketing & PR */

= Benefits of Rapid Betas =
* shorter verification turn-around time
* freed up RelEng/QA resources
* late-breaking beta issues can be much more easily resolved
* more user testing over the 6 week cycle
= Proposed Timeline =
* -4/23
** Consider major pain points, begin scoping work.
* 4/24-6/4
** Complete scoping work, begin implementation
** Communicate the plan to Mozilla community
** Move to Tuesday go, Wednesday ship? (see QA questions below)
** Any necessary in-product changes should land while FF15 is on m-c
* 6/5-7/16
** Complete implementation, begin process testing on Nightly/Aurora
* Week of 7/17
** Push out our first rapid beta while FF15 on mozilla-beta
= In-Product =
== Questions ==
* What do we do about non-admin users? What's the current experience? Can we back off on offering them an update by 7 days?
** should be possible be possible by only incrementing the update xml's appVersion attribute once a week see {{bug|753103}}
* Will the user be prompted at all to "apply the update now"? Can we disable that?
* If the user's browser downloads an update, then the user doesn't close and open their browser for 3 days, what build will be applied?
* Is the user going to be prompted every day to update, or will it be truely silent and the user won't notice it until the next day.
* Will our current beta users be happy with the additional bandwidth of potentially downloading updates every day?

== Blockers ==
* [https://wiki.mozilla.org/Background_Updates Background updates] will be landing in FF15.
** [[Silent_Update_updater | Feature page]]
** Tracking {{bug|307181}}, {{bug|753103}}

=Automation=
== Questions ==
* What are the communication points that need to happen (what needs to be communicated and when between the QA & RelEng)
* What can we do to keep automation running as smoothly as possible with known/unknown failures or automation glitches? ie: we will still need troubleshooting from QA when automation cuts out due to errors
== Blockers ==

= QA =
== Questions ==
* breakdown of when sign off has uncovered new regressions in a beta? (and if it has, was it through automation or manual (human) tests?)
** If we find that sign-off has not found new critical beta regressions, can we start shipping betas on Wednesdays after automated testing runs through (prior to rapid betas being implemented)? Bug verification, exploratory testing, and other smoke tests could continue out-of-band.
* can automating the release test plan be done against nightly/aurora in preparation for moving to faster beta releases?
* Can we automate mobile update testing? If so, we can even make the weekly push to the Play Store automatic.
== Blockers ==
* Update testing (and smoke tests) should be automated and worked into the build/push flow

=Support=
== Questions ==
* any pain points in supporting Aurora? (expand those into to-do items for supporting rapid betas)
== Blockers ==
= RelEng/IT =
== Questions ==
* any issues with automated pushsnip to beta channel?
** Needs to be gated on QA. We already automatically push to betatest. [[User:Catlee|Catlee]] 12:48, 13 April 2012 (PDT)
* can we add inputs from QA to incorporate the sign-off as part of automation?
* any possible issues with load (or mirrors) if we move to more frequent releases of beta on bouncer?
* Using the signing key appears to be a manual process currently, can this be automated?
** Already is! (except for android) - [[User:Catlee|Catlee]] 12:39, 13 April 2012 (PDT)
** note: upcoming osx10.8 signing is explicitly excluded
* Can we do the work associated with rapid betas be done in such a way that we could move back to weekly betas in the case of unforseen problems?
* Do we need to tag/package source for rapid betas?

== Blockers ==
* Tracking bug for RelEng work is {{bug|747168}}. Most notable items on it are:
** Automate android signing {{bug|705807}}
** Move master-side logic to client-side scripts: {{bug|748773}}, {{bug|748794}}, {{bug|748796}}, {{bug|748798}}, {{bug|748800}}
** Make mail notification work without a reconfig {{bug|749587}}
** Automate snippet optimization {{bug|748801}}
** Switch to using a different L10n url to get changesets for desktop: {{bug|751703}}, and keep the changeset info from each build in the manifest (to be created by releng as a replacement for tagging)

* unrelated but blocker: supporting new OS/platforms.

= Crash-Kill Team & Soccorro =
== Questions ==
* What are the implications of switching to rapid betas? How would crash analysis be different than m-c or m-a?
* Do we need to implement windowing over multiple build IDs to emulate having a large beta population on a single beta?
* What is a unit of 'enough' user testing data (days?) for getting feedback on a regression fix?
== Blockers ==
* Scoping happening [https://wiki.mozilla.org/Socorro:Rapid_Betas here]
* Tracking {{bug|752956}}
* [https://wiki.mozilla.org/Socorro:Rapid_Betas:Requirements Requirements]
* [https://wiki.mozilla.org/Socorro:Rapid_Betas:Implementation_Plan Implementation Plan]

= L10N =
== Answers/Resolutions ==
* Keep sign-offs on release and beta channel, continue without signoffs on aurora and central
* Drop the use of milestones at least for rapid betas
* Get l10n-changesets from urls that give the current signed-off state for a product/version
** These urls need to updated on migration day every six weeks
** These urls are already existing, using the av= keyword argument with the right code instead of a ms= keyword
== Questions ==
* What do we do with l10n milestones?
* Could we work towards automatically pulling from a beta branch? This doesn't really scale well.
* Could l10n_changesets be dynamically created from the csets on beta branch for locales in shipped_locales?
* Can l10n sign offs be automated? Test suites that check for anything other than string changes?

New questions:
* What happens with non-rapid betas, notably TB/SeaMonkey? '''(No change, continue as usual)'''
* Do we need a "sealed" status for release, or is that good to go without milestones, too? '''(That is up to the needs of the l10n drivers, do you want a tagged repo every 6 weeks when a release goes out?)'''

== Blockers ==
* None, but a releng bug on using the new url: {{bug|751703}}

= Release Management =
'''Update''' - RelEng (and lsblakk) met and discussed the complete process of releasing betas and have scoped the work involved in meeting this project's goals [https://wiki.mozilla.org/ReleaseEngineering/Rapid_Release_Nightly_Betas#Live_Notes here]
== Questions ==
* What should we call beta nightlies (Rapid Betas)?
* How do we communicate beta nightlies?
* The beta release process is a useful tool for verifying the final release process. If we change the final release process, how will we verify the changes or bring new people up to speed without affecting the timing of the final releases?
** Do we need to build in a slightly larger window for the final release to allow for these types of issues?
== Blockers ==
* Need to change the process of approving for Beta to first go through Aurora, for sake of risk mitigation
* We need to watch for more stretch across multiple versions of beta than we currently have across weekly betas
* Feature request: getting BuildIDs in Input to get more data on where feedback is coming from
* What's new page - either always on or always off but we'll need a better plan

= Metrics =
We did a sample analysis on the crash report data for beta for last 10 days of april.
The 9 out of the top 10 crashers in the 1st hour remain in the top 10 of the last hour of the 10 day period.
We probably will not be able to pick up enough reports to catch the rare crashes on day 1, so these will persist in subsequent builds and will be picked up later.

In summary:
- Using Rapid Builds we will be able to push bug fixes faster.
- Rare signatures will be picked up later (once enough reports come in) and in this regard Rapid Builds is not much different from weekly builds.

= Product Marketing & PR =
'''Update''' - Grace & Laura discussed; EJ added input; Laura discussed in channel meeting, wrote down answers.
== Questions & Responses ==
* This will have an impact on how we could deploy a What's New Page which we've planning to do for sometime. We will likely still be able to, but we'll have to coordinate much closer on when and how those pages are turned off and on. What would be the details of getting a paged turned on or off?
** No clear answer on this. This is not a blocker, but something to keep in mind for the future to find a solution.
* How will this effect release notes? Will we update them every day? Once a week?
** Will keep doing release notes the way we do Aurora--stand them up with initial release and make minor changes as needed; don't think we will see major changes between first release and end of the cycle.
* How will this effect how we track comments/feedback on Input?
** Yes, it will. Will need a way to correlate comments to buildIDs.
* Will this effect how we track ADUs/ADIs with metrics tools?
** Yes, Alex is filing a bug.
* How will users be alerted to the updates? Will it cause update fatigue?
** No because this will only be implemented after silent updates.
* Is this the new way of doing things or a short term thing we are testing?
** Its the plan for the foreseeable future, but may be changed depending on resources, needs, etc.
* Does this mean new features can land in beta?
** It makes it less risky to land features, but any feature additions will be discussed in depth before landing; don't think this will cause an increase in the landing of new features.
* Do we have to update our communications around what to expect for each channel?
** I don't think it does, apart from a general blog post announcing the change.
* Will this change the release timeline?
** No, this shouldn't effect release timeline at all.

== Blockers ==
* Blog Post communicating change on FoF; must be reviewed by PMMs and PR
* Alignment on naming (we don't see a reason to change the name and didn't like adding "rapid" to releases)
* Figuring out how to make release notes work for all audiences/communications
* This will impact if/when/how often we want to communicate about betas
* Updating all channel comms

Release Management/Rapid Betas

2012-05-10T22:07:57Z

Lmesa: /* Questions& Responses */

= Benefits of Rapid Betas =
* shorter verification turn-around time
* freed up RelEng/QA resources
* late-breaking beta issues can be much more easily resolved
* more user testing over the 6 week cycle
= Proposed Timeline =
* -4/23
** Consider major pain points, begin scoping work.
* 4/24-6/4
** Complete scoping work, begin implementation
** Communicate the plan to Mozilla community
** Move to Tuesday go, Wednesday ship? (see QA questions below)
** Any necessary in-product changes should land while FF15 is on m-c
* 6/5-7/16
** Complete implementation, begin process testing on Nightly/Aurora
* Week of 7/17
** Push out our first rapid beta while FF15 on mozilla-beta
= In-Product =
== Questions ==
* What do we do about non-admin users? What's the current experience? Can we back off on offering them an update by 7 days?
** should be possible be possible by only incrementing the update xml's appVersion attribute once a week see {{bug|753103}}
* Will the user be prompted at all to "apply the update now"? Can we disable that?
* If the user's browser downloads an update, then the user doesn't close and open their browser for 3 days, what build will be applied?
* Is the user going to be prompted every day to update, or will it be truely silent and the user won't notice it until the next day.
* Will our current beta users be happy with the additional bandwidth of potentially downloading updates every day?

== Blockers ==
* [https://wiki.mozilla.org/Background_Updates Background updates] will be landing in FF15.
** [[Silent_Update_updater | Feature page]]
** Tracking {{bug|307181}}, {{bug|753103}}

=Automation=
== Questions ==
* What are the communication points that need to happen (what needs to be communicated and when between the QA & RelEng)
* What can we do to keep automation running as smoothly as possible with known/unknown failures or automation glitches? ie: we will still need troubleshooting from QA when automation cuts out due to errors
== Blockers ==

= QA =
== Questions ==
* breakdown of when sign off has uncovered new regressions in a beta? (and if it has, was it through automation or manual (human) tests?)
** If we find that sign-off has not found new critical beta regressions, can we start shipping betas on Wednesdays after automated testing runs through (prior to rapid betas being implemented)? Bug verification, exploratory testing, and other smoke tests could continue out-of-band.
* can automating the release test plan be done against nightly/aurora in preparation for moving to faster beta releases?
* Can we automate mobile update testing? If so, we can even make the weekly push to the Play Store automatic.
== Blockers ==
* Update testing (and smoke tests) should be automated and worked into the build/push flow

=Support=
== Questions ==
* any pain points in supporting Aurora? (expand those into to-do items for supporting rapid betas)
== Blockers ==
= RelEng/IT =
== Questions ==
* any issues with automated pushsnip to beta channel?
** Needs to be gated on QA. We already automatically push to betatest. [[User:Catlee|Catlee]] 12:48, 13 April 2012 (PDT)
* can we add inputs from QA to incorporate the sign-off as part of automation?
* any possible issues with load (or mirrors) if we move to more frequent releases of beta on bouncer?
* Using the signing key appears to be a manual process currently, can this be automated?
** Already is! (except for android) - [[User:Catlee|Catlee]] 12:39, 13 April 2012 (PDT)
** note: upcoming osx10.8 signing is explicitly excluded
* Can we do the work associated with rapid betas be done in such a way that we could move back to weekly betas in the case of unforseen problems?
* Do we need to tag/package source for rapid betas?

== Blockers ==
* Tracking bug for RelEng work is {{bug|747168}}. Most notable items on it are:
** Automate android signing {{bug|705807}}
** Move master-side logic to client-side scripts: {{bug|748773}}, {{bug|748794}}, {{bug|748796}}, {{bug|748798}}, {{bug|748800}}
** Make mail notification work without a reconfig {{bug|749587}}
** Automate snippet optimization {{bug|748801}}
** Switch to using a different L10n url to get changesets for desktop: {{bug|751703}}, and keep the changeset info from each build in the manifest (to be created by releng as a replacement for tagging)

* unrelated but blocker: supporting new OS/platforms.

= Crash-Kill Team & Soccorro =
== Questions ==
* What are the implications of switching to rapid betas? How would crash analysis be different than m-c or m-a?
* Do we need to implement windowing over multiple build IDs to emulate having a large beta population on a single beta?
* What is a unit of 'enough' user testing data (days?) for getting feedback on a regression fix?
== Blockers ==
* Scoping happening [https://wiki.mozilla.org/Socorro:Rapid_Betas here]
* Tracking {{bug|752956}}
* [https://wiki.mozilla.org/Socorro:Rapid_Betas:Requirements Requirements]
* [https://wiki.mozilla.org/Socorro:Rapid_Betas:Implementation_Plan Implementation Plan]

= L10N =
== Answers/Resolutions ==
* Keep sign-offs on release and beta channel, continue without signoffs on aurora and central
* Drop the use of milestones at least for rapid betas
* Get l10n-changesets from urls that give the current signed-off state for a product/version
** These urls need to updated on migration day every six weeks
** These urls are already existing, using the av= keyword argument with the right code instead of a ms= keyword
== Questions ==
* What do we do with l10n milestones?
* Could we work towards automatically pulling from a beta branch? This doesn't really scale well.
* Could l10n_changesets be dynamically created from the csets on beta branch for locales in shipped_locales?
* Can l10n sign offs be automated? Test suites that check for anything other than string changes?

New questions:
* What happens with non-rapid betas, notably TB/SeaMonkey? '''(No change, continue as usual)'''
* Do we need a "sealed" status for release, or is that good to go without milestones, too? '''(That is up to the needs of the l10n drivers, do you want a tagged repo every 6 weeks when a release goes out?)'''

== Blockers ==
* None, but a releng bug on using the new url: {{bug|751703}}

= Release Management =
'''Update''' - RelEng (and lsblakk) met and discussed the complete process of releasing betas and have scoped the work involved in meeting this project's goals [https://wiki.mozilla.org/ReleaseEngineering/Rapid_Release_Nightly_Betas#Live_Notes here]
== Questions ==
* What should we call beta nightlies (Rapid Betas)?
* How do we communicate beta nightlies?
* The beta release process is a useful tool for verifying the final release process. If we change the final release process, how will we verify the changes or bring new people up to speed without affecting the timing of the final releases?
** Do we need to build in a slightly larger window for the final release to allow for these types of issues?
== Blockers ==
* Need to change the process of approving for Beta to first go through Aurora, for sake of risk mitigation
* We need to watch for more stretch across multiple versions of beta than we currently have across weekly betas
* Feature request: getting BuildIDs in Input to get more data on where feedback is coming from
* What's new page - either always on or always off but we'll need a better plan

= Metrics =
We did a sample analysis on the crash report data for beta for last 10 days of april.
The 9 out of the top 10 crashers in the 1st hour remain in the top 10 of the last hour of the 10 day period.
We probably will not be able to pick up enough reports to catch the rare crashes on day 1, so these will persist in subsequent builds and will be picked up later.

In summary:
- Using Rapid Builds we will be able to push bug fixes faster.
- Rare signatures will be picked up later (once enough reports come in) and in this regard Rapid Builds is not much different from weekly builds.

= Product Marketing & PR =
'''Update''' - Grace & Laura discussed; EJ added input; questions and blockers below.
== Questions & Responses ==
* This will have an impact on how we could deploy a What's New Page which we've planning to do for sometime. We will likely still be able to, but we'll have to coordinate much closer on when and how those pages are turned off and on. What would be the details of getting a paged turned on or off?
** No clear answer on this. This is not a blocker, but something to keep in mind for the future to find a solution.
* How will this effect release notes? Will we update them every day? Once a week?
** Will keep doing release notes the way we do Aurora--stand them up with initial release and make minor changes as needed; don't think we will see major changes between first release and end of the cycle.
* How will this effect how we track comments/feedback on Input?
** Yes, it will. Will need a way to correlate comments to buildIDs.
* Will this effect how we track ADUs/ADIs with metrics tools?
** Yes, Alex is filing a bug.
* How will users be alerted to the updates? Will it cause update fatigue?
** No because this will only be implemented after silent updates.
* Is this the new way of doing things or a short term thing we are testing?
** Its the plan for the foreseeable future, but may be changed depending on resources, needs, etc.
* Does this mean new features can land in beta?
** It makes it less risky to land features, but any feature additions will be discussed in depth before landing; don't think this will cause an increase in the landing of new features.
* Do we have to update our communications around what to expect for each channel?
** I don't think it does, apart from a general blog post announcing the change.
* Will this change the release timeline?
** No, this shouldn't effect release timeline at all.

== Blockers ==
* Blog Post communicating change on FoF; must be reviewed by PMMs and PR
* Alignment on naming (we don't see a reason to change the name and didn't like adding "rapid" to releases)
* Figuring out how to make release notes work for all audiences/communications
* This will impact if/when/how often we want to communicate about betas
* Updating all channel comms

Release Management/Rapid Betas

2012-05-10T22:01:16Z

Lmesa: /* Questions */

= Benefits of Rapid Betas =
* shorter verification turn-around time
* freed up RelEng/QA resources
* late-breaking beta issues can be much more easily resolved
* more user testing over the 6 week cycle
= Proposed Timeline =
* -4/23
** Consider major pain points, begin scoping work.
* 4/24-6/4
** Complete scoping work, begin implementation
** Communicate the plan to Mozilla community
** Move to Tuesday go, Wednesday ship? (see QA questions below)
** Any necessary in-product changes should land while FF15 is on m-c
* 6/5-7/16
** Complete implementation, begin process testing on Nightly/Aurora
* Week of 7/17
** Push out our first rapid beta while FF15 on mozilla-beta
= In-Product =
== Questions ==
* What do we do about non-admin users? What's the current experience? Can we back off on offering them an update by 7 days?
** should be possible be possible by only incrementing the update xml's appVersion attribute once a week see {{bug|753103}}
* Will the user be prompted at all to "apply the update now"? Can we disable that?
* If the user's browser downloads an update, then the user doesn't close and open their browser for 3 days, what build will be applied?
* Is the user going to be prompted every day to update, or will it be truely silent and the user won't notice it until the next day.
* Will our current beta users be happy with the additional bandwidth of potentially downloading updates every day?

== Blockers ==
* [https://wiki.mozilla.org/Background_Updates Background updates] will be landing in FF15.
** [[Silent_Update_updater | Feature page]]
** Tracking {{bug|307181}}, {{bug|753103}}

=Automation=
== Questions ==
* What are the communication points that need to happen (what needs to be communicated and when between the QA & RelEng)
* What can we do to keep automation running as smoothly as possible with known/unknown failures or automation glitches? ie: we will still need troubleshooting from QA when automation cuts out due to errors
== Blockers ==

= QA =
== Questions ==
* breakdown of when sign off has uncovered new regressions in a beta? (and if it has, was it through automation or manual (human) tests?)
** If we find that sign-off has not found new critical beta regressions, can we start shipping betas on Wednesdays after automated testing runs through (prior to rapid betas being implemented)? Bug verification, exploratory testing, and other smoke tests could continue out-of-band.
* can automating the release test plan be done against nightly/aurora in preparation for moving to faster beta releases?
* Can we automate mobile update testing? If so, we can even make the weekly push to the Play Store automatic.
== Blockers ==
* Update testing (and smoke tests) should be automated and worked into the build/push flow

=Support=
== Questions ==
* any pain points in supporting Aurora? (expand those into to-do items for supporting rapid betas)
== Blockers ==
= RelEng/IT =
== Questions ==
* any issues with automated pushsnip to beta channel?
** Needs to be gated on QA. We already automatically push to betatest. [[User:Catlee|Catlee]] 12:48, 13 April 2012 (PDT)
* can we add inputs from QA to incorporate the sign-off as part of automation?
* any possible issues with load (or mirrors) if we move to more frequent releases of beta on bouncer?
* Using the signing key appears to be a manual process currently, can this be automated?
** Already is! (except for android) - [[User:Catlee|Catlee]] 12:39, 13 April 2012 (PDT)
** note: upcoming osx10.8 signing is explicitly excluded
* Can we do the work associated with rapid betas be done in such a way that we could move back to weekly betas in the case of unforseen problems?
* Do we need to tag/package source for rapid betas?

== Blockers ==
* Tracking bug for RelEng work is {{bug|747168}}. Most notable items on it are:
** Automate android signing {{bug|705807}}
** Move master-side logic to client-side scripts: {{bug|748773}}, {{bug|748794}}, {{bug|748796}}, {{bug|748798}}, {{bug|748800}}
** Make mail notification work without a reconfig {{bug|749587}}
** Automate snippet optimization {{bug|748801}}
** Switch to using a different L10n url to get changesets for desktop: {{bug|751703}}, and keep the changeset info from each build in the manifest (to be created by releng as a replacement for tagging)

* unrelated but blocker: supporting new OS/platforms.

= Crash-Kill Team & Soccorro =
== Questions ==
* What are the implications of switching to rapid betas? How would crash analysis be different than m-c or m-a?
* Do we need to implement windowing over multiple build IDs to emulate having a large beta population on a single beta?
* What is a unit of 'enough' user testing data (days?) for getting feedback on a regression fix?
== Blockers ==
* Scoping happening [https://wiki.mozilla.org/Socorro:Rapid_Betas here]
* Tracking {{bug|752956}}
* [https://wiki.mozilla.org/Socorro:Rapid_Betas:Requirements Requirements]
* [https://wiki.mozilla.org/Socorro:Rapid_Betas:Implementation_Plan Implementation Plan]

= L10N =
== Answers/Resolutions ==
* Keep sign-offs on release and beta channel, continue without signoffs on aurora and central
* Drop the use of milestones at least for rapid betas
* Get l10n-changesets from urls that give the current signed-off state for a product/version
** These urls need to updated on migration day every six weeks
** These urls are already existing, using the av= keyword argument with the right code instead of a ms= keyword
== Questions ==
* What do we do with l10n milestones?
* Could we work towards automatically pulling from a beta branch? This doesn't really scale well.
* Could l10n_changesets be dynamically created from the csets on beta branch for locales in shipped_locales?
* Can l10n sign offs be automated? Test suites that check for anything other than string changes?

New questions:
* What happens with non-rapid betas, notably TB/SeaMonkey? '''(No change, continue as usual)'''
* Do we need a "sealed" status for release, or is that good to go without milestones, too? '''(That is up to the needs of the l10n drivers, do you want a tagged repo every 6 weeks when a release goes out?)'''

== Blockers ==
* None, but a releng bug on using the new url: {{bug|751703}}

= Release Management =
'''Update''' - RelEng (and lsblakk) met and discussed the complete process of releasing betas and have scoped the work involved in meeting this project's goals [https://wiki.mozilla.org/ReleaseEngineering/Rapid_Release_Nightly_Betas#Live_Notes here]
== Questions ==
* What should we call beta nightlies (Rapid Betas)?
* How do we communicate beta nightlies?
* The beta release process is a useful tool for verifying the final release process. If we change the final release process, how will we verify the changes or bring new people up to speed without affecting the timing of the final releases?
** Do we need to build in a slightly larger window for the final release to allow for these types of issues?
== Blockers ==
* Need to change the process of approving for Beta to first go through Aurora, for sake of risk mitigation
* We need to watch for more stretch across multiple versions of beta than we currently have across weekly betas
* Feature request: getting BuildIDs in Input to get more data on where feedback is coming from
* What's new page - either always on or always off but we'll need a better plan

= Metrics =
We did a sample analysis on the crash report data for beta for last 10 days of april.
The 9 out of the top 10 crashers in the 1st hour remain in the top 10 of the last hour of the 10 day period.
We probably will not be able to pick up enough reports to catch the rare crashes on day 1, so these will persist in subsequent builds and will be picked up later.

In summary:
- Using Rapid Builds we will be able to push bug fixes faster.
- Rare signatures will be picked up later (once enough reports come in) and in this regard Rapid Builds is not much different from weekly builds.

= Product Marketing & PR =
'''Update''' - Grace & Laura discussed; EJ added input; questions and blockers below.
== Questions& Responses ==
* This will have an impact on how we could deploy a What's New Page which we've planning to do for sometime. We will likely still be able to, but we'll have to coordinate much closer on when and how those pages are turned off and on. What would be the details of getting a paged turned on or off?
* How will this effect release notes? Will we update them every day? Once a week?
* How will this effect how we track comments/feedback on Input?
* Will this effect how we track ADUs/ADIs with metrics tools?
* How will users be alerted to the updates? Will it cause update fatigue?
* Is this the new way of doing things or a short term thing we are testing?
* Does this mean new features can land in beta?
* Do we have to update our communications around what to expect for each channel?
* Will this change the release timeline?

== Blockers ==
* Blog Post communicating change on FoF; must be reviewed by PMMs and PR
* Alignment on naming (we don't see a reason to change the name and didn't like adding "rapid" to releases)
* Figuring out how to make release notes work for all audiences/communications
* This will impact if/when/how often we want to communicate about betas
* Updating all channel comms

Firefox/Planning/2012-05-09

2012-05-09T18:04:23Z

Lmesa: /* Marketing, Press & Public Reaction */

<center>[[Firefox/Planning/{{#time: Y-m-d | {{SUBPAGENAME}} -1 week}}|« previous week]] | [[Firefox/DeliveryMeetings|index]] | [[Firefox/Planning/{{#time: Y-m-d | {{SUBPAGENAME}} +1 week}}|next week »]]</center>

'''Planning Meeting Details'''
* Wednesdays - 11:00am PDT, 18:00 UTC
* Mountain View Offices: Warp Core Conference Room
* Toronto Offices: Finch Conference Room
* [irc://irc.mozilla.org/planning irc.mozilla.org #planning] for backchannel
* (the [[Platform#Meetings|developer meeting]] takes place on Tuesdays)

'''Video/Teleconference Details - NEW'''
* 650-903-0800 or 650-215-1282 x92 Conf# '''95312''' (US/INTL)
* 1-800-707-2533 (pin 369) Conf# '''95312''' (US)
* Vidyo Room: Warp Core
* Vidyo [https://v.mozilla.com/flex.html?roomdirect.html&key=UK1zyrd7Vhym Guest URL]

{{Notes}}

__FORCETOC__

== Actions from Last Week ==
* dcm to find updated states of sdk usage in new addons
** In [https://wiki.mozilla.org/Firefox/Planning/2012-05-09#Add-on_SDK Add-on SDK Section!]
* thunder/mconnor - update on identity+sync
* michelleluna - look at gmail feedback for aurora this week (doesn't reload); Answer: there is no input data to suggest a widepsread reloading Gmail issue in Firefox, I see only 6 comments out of 999 related to Gmail and none about not reloading, see input.mozilla.org/en-US/?product=firefox&version=14.0a2&date_start=2012-04-25&date_end=&q= A more generic search for 'google' also surfaces no comments about mail issues.

== Schedule & Progress on [[Releases|Upcoming Releases]] ==
=== Kilimanjaro ===

===Firefox Desktop ===
==== Release (12, 10esr, 3.6) ====
* Automatic updates from 3.6 to 12 are proceeding in {{bug|753006}} – Please prepare automatic updates for FF3.6 to FF12
** 3.6.28->12 updates are already live

==== Beta (13) ====
* We've just built our third FF13 beta

==== Aurora (14) ====

==== Nightly (15) ====
* Owen Carpenter, John Rietveld, Devon Sayles, and Zuhao (Joe) Chen from Michigan State's CSE Capstone program landed in-content prefs (preffed off) and tests into m-c last night. To see this great work, set browser.preferences.inContent to true. Congratulations to that team. Thanks to Jared Wein for his mentoring and to Unfocused for his code reviews. See [http://msujaws.wordpress.com/2012/01/09/in-content-preferences-for-firefox-may-be-here-in-16-weeks/ In-Content Preferences for Firefox may be here in 16 weeks] for .ore,
* {{Bug|650353}} have one global object per compartment
* {{Bug|752877}} Cut wrappers after firing [inner,outer]-window-destroyed.
* {{Bug|716439}} Implement clipping to rectangles with rounded corners on the GPU
* {{Bug|674225}} support the Opus voice codec in <nowiki><audio></nowiki> and <nowiki><video></nowiki> elements
* {{Bug|641892}} Support showing multiple popup notification icons at the same time
* {{Bug|743877}} tab switching shouldn't occur off a timeout
* {{Bug|664918}} Infrastructure for media stream graph processing
* {{Bug|650988}} Do image scaling on the GPU
* {{Bug|748785}} Enable NPAPI Async drawing model by default on windows
* {{Bug|166240}} Implement D3E KeyboardEvent.location (except JOYSTICK)
* {{Bug|478927}} Need a way from chrome to know when error pages load
* {{Bug|726366}} spdy should support tunnel through http proxy
* {{Bug|377624}} Implement the accept attribute for the form and file upload controls form "image/*"

=== Firefox Mobile ===

=== Services ===
* read the wiki update
==== Firefox Sync ====
* Sync 2.0 & Sign into Browser have separated into two projects
** ping :ally if you have questions about what this means
* Along with mobile, _this_ close to the fennec beta
==== Apps In the Cloud Server ====
* keeps on rocking in the free world

=== Add-on SDK ===

Release (1.6 -> Firefox 11, 12)

% of all new add-ons uploaded to AMO that are built with Add-on SDK (these are rough numbers identified only by GUIDs beginning with "jid")
Jan 35.27%
Feb 29.2%
Mar 34.15%
Apr 30.34%

Stabilization (1.7 -> Firefox 12, 13)
* [https://groups.google.com/d/msg/mozilla-labs-jetpack/-/HxdSZrwnFo4J Released 1.7RC2 yesterday] - please test
* On track to release 15 May 2012 (next Tuesday!)

Development (1.8 -> Firefox 13, 14)
* On track to merge to Stabilization 15 May 2012
* Spring cleaning! We need add-on developers to give comments on a couple of issues on items we want to change. [http://blog.mozilla.org/addons/2012/05/07/spring-cleaning-changes-to-require-and-self-in-the-sdk/ Much more detail on the add-ons blog.]
* Memshrink goes on - and we have decisions to make on what to do about SDK-based add-ons on AMO that use very old versions of the SDK with known leaks.
** [http://blog.mozilla.org/addons/2012/05/07/memshrink-progress-leaky-add-ons-and-older-sdk-versions/ The quick answer is for everyone with an add-on to rebuild it with a new version of the SDK.]
** [https://bugzilla.mozilla.org/show_bug.cgi?id=751466 The not-so-quick answer is being discussed.]

===Identity===

===Apps===
* Firefox Desktop 14 (Aurora) - landed
** Looking to back out this functionality - {{bug|750936}}
** Native Install
** Chromeless launch of apps

* Mozillian Marketplace Release is out! We need feedback!
** Please download Firefox Nightly Desktop (Fx15)
** Have a look at the [[/Marketplace/Mozillian_Preview |wiki]] to learn more about the testing procedure.
** If you run into any hiccups, you can report them to apps-feedback@mozilla.com.
** Once you’re done, there’s also an [http://qsurvey.mozilla.com/s3/mozillianspreview online survey] for you to fill out.

* Firefox Desktop 15 (Nightly)
** Working on fixing bugs - mostly fit and polish to fit Kilimanjaro requirements

* Firefox Mobile 15 (Nightly) - in progress
** Work started in Fx14 continues in 15.
** Proposed marketplace bundling with Fennec is an open issue. See {{bug|738545}}

* Apps in the Cloud
** AITC client continues
** AITC Server - Completed

===Developer Experience===

* [[DevTools/Features/ResponsiveView|Responsive Design View]] has been added to Kilimanjaro. Currently targeting Firefox 15.
* We're also still targeting Firefox 15 for the JavaScript Debugger, which also has remote debugging capability for Android and B2G.
* Also aiming for Firefox 15 for the [[DevTools/Features/DeveloperToolbar|Developer Toolbar]]. This feature will start pulling the tools together and providing quick keyboard access via a command line.
* The last major missing piece of functionality for the Firefox developer tools is a [[DevTools/Features/NetworkView|network view]]. Firebug leader Jan (Honza) Odvarko has extracted this functionality from Firebug into a separate addon called [https://github.com/janodvarko/httpmonitor HTTP Monitor]. The goal is to try sharing this code between Firebug and Firefox. They're also working on making this remotable like the JavaScript Debugger. We're hoping to have this functionality in Firefox soon, but not Firefox 15.
* The Apps developer ecosystem team is making good progress on [[Apps/Ecosystem|their projects]], including the first documentation "track" that takes web developers from beginning to end through an application. They are also building a "bootstrap" application template that Apps developers can use to get their projects started. More news on these as we get closer to release. These are part of Kilimanjaro.

== Feedback Summary ==
=== Desktop ===
Firefox 12 issues summary:

We currently have a 5% increase in issues over Firefox 11 at the three week mark. This seems to be a combination of issues including:

PDF Issues on Mac - https://bugzilla.mozilla.org/show_bug.cgi?id=747073
[http://input.mozilla.org/en-US/opinion/2909934]
[http://input.mozilla.org/en-US/opinion/2909278]
[http://support.mozilla.com/en-US/questions/775819]

Plugins/Check issue - Resolved - https://bugzilla.mozilla.org/show_bug.cgi?id=752232
[http://input.mozilla.org/en-US/opinion/2907452]
[http://input.mozilla.org/en-US/opinion/2907420]
[http://support.mozilla.com/en-US/questions/926756]

Copy/Paste Image - Fixed - https://bugzilla.mozilla.org/show_bug.cgi?id=749527
[https://support.mozilla.org/en-US/questions/926093]
[http://input.mozilla.org/en-US/?q=copy+image&product=firefox&version=12.0&sentiment=sad&date_start=2012-04-07]

Firefox 12 incorrectly caching pages - Bug filed - https://bugzilla.mozilla.org/show_bug.cgi?id=751753
[https://support.mozilla.org/en-US/questions/926043]

Incompatible Norton Toolbar: Need to update norton 360 and norton internet security suite.
[https://support.mozilla.org/en-US/questions/925899]
[http://input.mozilla.org/en-US/?q=norton&product=firefox&version=12.0&sentiment=sad&date_start=2012-04-07]

Bookmarks* Could be just lots of updates from older version. Some reports that bookmarks are missing.
[http://input.mozilla.org/en-US/opinion/2903145]
[http://input.mozilla.org/en-US/opinion/2906021]
[http://support.mozilla.com/en-US/questions/925927]
[https://support.mozilla.org/en-US/questions/926621]
Possibly related TB issue outstanding: [https://getsatisfaction.com/mozilla_messaging/tags/bug_750781] Could be related to other slowness reports we are getting.

FF12 praise summary, down 6% from FF11:

fast:
[http://input.mozilla.org/en-US/opinion/2914859]
[http://input.mozilla.org/en-US/opinion/2914763]
[http://input.mozilla.org/en-US/opinion/2913147]

ui:
[http://input.mozilla.org/en-US/opinion/2914504]
[http://input.mozilla.org/en-US/opinion/2914429]

stable:
[http://input.mozilla.org/en-US/opinion/2912898]

FF13 beta issues summary:

PDF on Mac
[http://input.mozilla.org/en-US/?product=firefox&sentiment=sad&date_end=&date_start=2012-05-02&platform=mac&version=13.0&q=pdf 96 comments]

Flash/video
[http://input.mozilla.org/en-US/?q=flash&product=firefox&version=13.0&date_start=2012-05-02&date_end=&sentiment=sad 127 comments]
[http://input.mozilla.org/en-US/?product=firefox&sentiment=sad&date_end=&date_start=2012-05-02&version=13.0&q=video 151 comments]

FF13 beta praise summary:

Smooth scrolling, well-liked:
[http://input.mozilla.org/en-US/?product=firefox&sentiment=happy&date_end=&date_start=2012-05-02&version=13.0&q=scroll 67 comments]

tab screen:
[http://input.mozilla.org/en-US/opinion/2910920]
[http://input.mozilla.org/en-US/opinion/2903849]
[http://input.mozilla.org/en-US/opinion/2901745]

new start page:
[http://input.mozilla.org/en-US/opinion/2914780]
[http://input.mozilla.org/en-US/opinion/2914221]
[http://input.mozilla.org/en-US/opinion/2911441]

FF14 aurora issues:

Flash:
[http://input.mozilla.org/en-US/opinion/2912569]
[http://input.mozilla.org/en-US/opinion/2897512]

slow/crashy:
[http://input.mozilla.org/en-US/opinion/2914677]
[http://input.mozilla.org/en-US/opinion/2914659]
[http://input.mozilla.org/en-US/opinion/2913496]
[http://input.mozilla.org/en-US/opinion/2912475]

FF14 aurora praise:

Design:
[http://input.mozilla.org/en-US/opinion/2914877]

Tools:
[http://input.mozilla.org/en-US/opinion/2914446]

Autocomplete URLs:
[http://input.mozilla.org/en-US/opinion/2904424]
[http://input.mozilla.org/en-US/opinion/2900517]
[http://input.mozilla.org/en-US/opinion/2897523]

full screen:
[http://input.mozilla.org/en-US/opinion/2907490]
[http://input.mozilla.org/en-US/opinion/2896967]

download manager:
[http://input.mozilla.org/en-US/opinion/2909392]
[http://input.mozilla.org/en-US/opinion/2911660]

FF15 Issues:
download manager feedback:
[http://input.mozilla.org/en-US/opinion/2914836]
[http://input.mozilla.org/en-US/opinion/2914236]
[http://input.mozilla.org/en-US/opinion/2903568]
[http://input.mozilla.org/en-US/opinion/2896528]

FF15 Praise:
download manager:
[http://input.mozilla.org/en-US/opinion/2911867]
[http://input.mozilla.org/en-US/opinion/2904560]

pdf viewer:
[http://input.mozilla.org/en-US/opinion/2887050]

=== Mobile ===

== UX & User Research ==
=== UX Design ===

* [sign-in] Updated interaction flow (desktop): http://people.mozilla.com/~zfang/SignIn/Home.html (Zhenshuo)
* [metro] Video sketch/walkthrough of metro Firefox interactions (Yuan)
** https://www.dropbox.com/s/0nfd2taz3ap8n37/FX%20Metro%20-%20Start%20Page.mov
** blog post forthcoming shortly; please don't link too widely yet before we move it to vimeo, etc.
* [desktop] First steps on simplifying preferences; [https://people.mozilla.com/~zfang/Preferences/TestPilotData/assets/fallback/index.html initial look at pref usage], [https://etherpad.mozilla.org/Preferences improvement ideas] (Zhenshuo)
* [Android] (ibarlow)
** Tablet UI specs in bugs and work beginning - [http://ianbarlow.wordpress.com/?p=344&shareadraft=4faaa4c04bb86 preview of a blog post with all the bug numbers] -- we'll be publishing this post phone-beta
** phone - exploratory work on menu structure and first-run
* [B2G] Firefox designs stable; B2G workweek this week (Larissa)

== '''Market Insights''' ==
=== Desktop / Platform ===
==== Android ====
* In an interesting experiment, a development team led by Miguel de Icaza [http://www.zdnet.com/blog/microsoft/xamarins-port-of-android-to-microsofts-c-five-questions-and-answers/12637 ported much of the Android OS' environment] to C#.
==== Security ====
* Adobe [http://www.computerworld.com/s/article/9226921/Adobe_preps_silent_Flash_updates_for_Macs released] a new beta of Flash Player for Mac OS X that supports silent updates.
* Concern was raised in the press that the impending arrival of Mac OS X Mountain Lion will mean that [http://www.computerworld.com/s/article/9226949/Half_of_all_Macs_will_lack_access_to_security_updates_by_summer nearly half of all Mac users will no longer receive security patches]
==== Microsoft ====
* Microsoft has started mailing [http://www.zdnet.com/blog/microsoft/microsoft-schedules-windows-phone-developer-summit-for-june/12631 "Save the Date"] invitations to Windows Phone developers for June 20-21 conference in San Francisco.
==== Opera ====
* Opera [http://www.opera.com/company/investors/ posted their Q1 2012 financial results]. Total revenue for the quarter was $47m, up 28% from the previous year, and net income was up 76%.
==== Research in Motion ====
* RIM posted the [http://devblog.blackberry.com/2012/05/blackberry-10-bbui/ latest version of bbUI], their HTML5 toolkit that makes HTML5 apps work more seamlessly on their platform.
==== Tizen ====
* Sprint, the American wireless carrier, announced that it was [http://www.businesswire.com/news/home/20120507006323/en/Sprint-Joins-Tizen-Association joining the Tizen Association]
* Tizen also [http://www.tizenexperts.com/2012/05/expect-2012-tizen-developer-conference/ announced more details] about their upcoming developer conference, and noted that most of the sessions would be streamed over the web.
==== WebKit ====
* The WebKit Inspector tool now offers [http://updates.html5rocks.com/2012/05/Websocket-Frame-Inspection-now-in-Chrome-DevTools web socket packet inspection]
==== W3C ====
* [http://www.webmonkey.com/2012/05/new-proposal-could-end-the-css-prefix-madness/ A new proposal] by W3C member Florian Rivoal offers a potential solution to the CSS vendor-prefix issue. It would require browser vendors to support both prefixed and unprefixed features from day one, with aliases between the two.
==== Other ====
* The Trustworthy Internet Movement launched [https://www.trustworthyinternet.org/ssl-pulse/ SSLPulse], a "continuous and global dashboard for monitoring the quality of SSL support across the top one million web sites. "
* An [http://www.technologyreview.com/business/40319/#.T6fn_4Jf8dg.twitter interesting piece by Technology Review magazine] about how they, and other magazine and newspaper publishers are looking to move away from proprietary platforms and to HTML5.

== Marketing, Press & Public Reaction ==
* Working on video for new tab and new home page for next GA release
* Working on the WN page for next release (will be localized).
* Work underway for blog posts for next round of Firefox releases.

== Questions, Comments, FYI ==

== Actions this week ==

Release Management/Rapid Betas

2012-05-07T21:33:53Z

Lmesa:

Firefox/Channels/Meetings/2012-05-03

2012-05-03T21:19:39Z

Lmesa: /* Marketing/Communications */

<center>[[Firefox/Channels/Meetings/{{#time: Y-m-d | {{SUBPAGENAME}} -1 week}}|« previous week]] | [[Firefox/Channels/Meetings |index]] | [[Firefox/Channels/Meetings/{{#time: Y-m-d | {{SUBPAGENAME}} +1 week}}|next week »]]</center>

'''Channel Meeting Details'''
* Tuesdays and Thursday - 2:00pm PDT, 21:00 UTC
* Mountain View Offices: Warp Core Conference Room
* [irc://irc.mozilla.org/planning irc.mozilla.org #planning] for backchannel

'''Video/Teleconference Details - NEW'''
* 650-903-0800 or 650-215-1282 x92 Conf# '''95312''' (US/INTL)
* 1-800-707-2533 (pin 369) Conf# '''95312''' (US)
* Vidyo Room: Warp Core
* Vidyo [https://v.mozilla.com/flex.html?roomdirect.html&key=UK1zyrd7Vhym Guest URL]

{{Notes}}

__FORCETOC__

== Previous Actions ==
* <strike>Alex - make sure everybody who needs to be around to discuss Flash beta is at our next channel meeting</strike>

== Schedule Update ==
* We are [https://mail.mozilla.com/home/akeybl@mozilla.com/Release%20Management.html?view=month&date=20120503 here] on the schedule - the bugs [https://bugzilla.mozilla.org/buglist.cgi?field0-3-0=cf_status_firefox13;type0-1-0=notequals;value0-4-0=verified;field0-1-0=cf_status_firefox13;field0-0-0=cf_tracking_firefox13;type0-4-0=notequals;value0-3-0=unaffected;query_format=advanced;value0-2-0=fixed;value0-1-0=wontfix;type0-3-0=notequals;field0-2-0=cf_status_firefox13;field0-4-0=cf_status_firefox13;type0-0-0=equals;value0-0-0=%2B;type0-2-0=notequals;list_id=3016729 tracked for FF13] is a fairly manageable burndown list at this point
** Engineers and engineering managers have been notified of outstanding tracked bugs

* Pushed out a new desupport hotfix (20120430.01) to fix over-prompting on Tuesday
* 13.0b1 was unthrottled yesterday
* 3.6 EOL MU have been pushed live and signed off yesterday
* 13.0b2 went out today
* We're shooting for a FN14 beta build #2 on 5/8, Google Play store testing is ongoing

* Tuesday 5/8 is the earliest that we'll go out with automatic updates for FF3.6 to FF12 (bugs incoming)

==Add-ons==
* {{bug|750387}} – consider blocklisting Adobe Reader (10.1.3)

== Stability ==
* Q: How can we start looking at top crash lists for Windows 8 and OS X 10.8 in conjunction with pre-release SW testing?

===Aurora===
 
===Beta===
 
===Release===
 

== QA ==
===Aurora===
 
===Beta===
QAWANTED ([http://bit.ly/IhfxAz query])
* {{bug|729507}} Crash in JSObject::finish - unable to reproduce crash with Yandex, any other leads we can pursue?

Nightly Betas Proposal
* Daily checkpoint for automation (as we do now with Nightly & Aurora)
* Staggered weekly checkpoint for smoketests, feature sign-offs, and exploratory testing
* Weekly checkpoint for bug fix verification progress, tracking to 0-bugs before release
* Should also do more to encourage a wider dog-fooding audience
* Q) How do we do a dry-run with weekly Betas?

Pre-release Software Proposal
* Current Coverage:
** Marcia dog-foods OSX 10.8 "once in a while", I'm not sure we have anyone doing the same for Win8
** Marcia dog-foods the official Flash Betas when they appear on labs.adobe.com
** Flash is tested every week in our Firefox Beta sign-offs (mostly regression tests against the current Flash release)
* Proposal: treat pre-release OS and Flash as "features"
** If OSX 10.8 is due out around the same time as Firefox 14 (June), add it to the "feature sign-offs" for Firefox 14 (marcia)
** If Win 8 is due out around the same time as Firefox 16 (October), add it to the "feature sign-offs" for Firefox 16 (juanb)
** Adobe puts out weekly sandboxed Betas; once a week we put this through a suite of regression and "feature" tests against the lastest Firefox Beta (ashughes)

== RelEng ==
 
== Marketing/Communications ==
* Metrics update: I think ADUs are back ; to normal.
** only 1.7% off all ADUs from last week 3.1% off of two weeks ago.

 

== Roundtable ==
* Pre-release Flash (and OS) testing

* Mobile Test Drivers (MTD)
** Email sent to all@ and everyone@ netted 45 more testers (41 employee, 4 volunteer)
** Keep encouraging people to test Fennec Native Android - see [[Mobile/Testdrivers_Program/How_To/Test|Testing tasks]]

* Rapid Betas update
** L10n scoping for rapid betas, no blockers there
** How is crashkill/socorro doing?
** Complete report on the implementation to go out next week, we'll review bugs on Tuesday (5/8) in the channel meeting

== Actions ==
 
== Triage ==
=== Aurora Queries ===
* [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=ALL+flag%3Aapproval-mozilla-aurora%3F&order=Bug+Number '''Approval requests''']
* [https://bugzilla.mozilla.org/buglist.cgi?field0-0-0=cf_tracking_firefox{{AURORA_VERSION}}&resolution=---&resolution=DUPLICATE&query_format=advanced&type0-0-0=equals&value0-0-0=%3F&order=Bug%20Number&list_id=1793640 '''Tracking noms''']
* [https://bugzilla.mozilla.org/buglist.cgi?field1-0-0=cf_status_firefox{{AURORA_VERSION}};type0-0-0=equals;value0-0-0=%2B;field0-0-0=cf_tracking_firefox{{AURORA_VERSION}};type1-0-0=notregexp;value1-0-0=%28fixed|wontfix|unaffected|verified%29;order=Bug%20Number '''Unresolved Tracking Bugs for FF{{AURORA_VERSION}}''']

=== Beta Queries ===
* [https://bugzilla.mozilla.org/buglist.cgi?&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=approval-mozilla-beta%3F&order=Bug%20Number '''Approval requests''']
* [https://bugzilla.mozilla.org/buglist.cgi?&field0-0-0=cf_tracking_firefox{{BETA_VERSION}}&type0-0-0=equals&value0-0-0=%3F&order=Bug%20Number '''Tracking noms''']
* [https://bugzilla.mozilla.org/buglist.cgi?field1-0-0=cf_status_firefox{{BETA_VERSION}};type0-0-0=equals;value0-0-0=%2B;field0-0-0=cf_tracking_firefox{{BETA_VERSION}};type1-0-0=notregexp;value1-0-0=%28fixed|wontfix|unaffected|verified%29;order=Bug%20Number '''Unresolved Tracking Bugs for FF{{BETA_VERSION}}''']

Firefox/Channels/Meetings/2012-05-03

2012-05-03T21:12:22Z

Lmesa: /* Marketing/Communications */

<center>[[Firefox/Channels/Meetings/{{#time: Y-m-d | {{SUBPAGENAME}} -1 week}}|« previous week]] | [[Firefox/Channels/Meetings |index]] | [[Firefox/Channels/Meetings/{{#time: Y-m-d | {{SUBPAGENAME}} +1 week}}|next week »]]</center>

'''Channel Meeting Details'''
* Tuesdays and Thursday - 2:00pm PDT, 21:00 UTC
* Mountain View Offices: Warp Core Conference Room
* [irc://irc.mozilla.org/planning irc.mozilla.org #planning] for backchannel

'''Video/Teleconference Details - NEW'''
* 650-903-0800 or 650-215-1282 x92 Conf# '''95312''' (US/INTL)
* 1-800-707-2533 (pin 369) Conf# '''95312''' (US)
* Vidyo Room: Warp Core
* Vidyo [https://v.mozilla.com/flex.html?roomdirect.html&key=UK1zyrd7Vhym Guest URL]

{{Notes}}

__FORCETOC__

== Previous Actions ==
* <strike>Alex - make sure everybody who needs to be around to discuss Flash beta is at our next channel meeting</strike>

== Schedule Update ==
* We are [https://mail.mozilla.com/home/akeybl@mozilla.com/Release%20Management.html?view=month&date=20120503 here] on the schedule - the bugs [https://bugzilla.mozilla.org/buglist.cgi?field0-3-0=cf_status_firefox13;type0-1-0=notequals;value0-4-0=verified;field0-1-0=cf_status_firefox13;field0-0-0=cf_tracking_firefox13;type0-4-0=notequals;value0-3-0=unaffected;query_format=advanced;value0-2-0=fixed;value0-1-0=wontfix;type0-3-0=notequals;field0-2-0=cf_status_firefox13;field0-4-0=cf_status_firefox13;type0-0-0=equals;value0-0-0=%2B;type0-2-0=notequals;list_id=3016729 tracked for FF13] is a fairly manageable burndown list at this point
** Engineers and engineering managers have been notified of outstanding tracked bugs

* Pushed out a new desupport hotfix (20120430.01) to fix over-prompting on Tuesday
* 13.0b1 was unthrottled yesterday
* 3.6 EOL MU have been pushed live and signed off yesterday
* 13.0b2 went out today
* We're shooting for a FN14 beta build #2 on 5/8, Google Play store testing is ongoing

* Tuesday 5/8 is the earliest that we'll go out with automatic updates for FF3.6 to FF12 (bugs incoming)

==Add-ons==
* {{bug|750387}} – consider blocklisting Adobe Reader (10.1.3)

== Stability ==
* Q: How can we start looking at top crash lists for Windows 8 and OS X 10.8 in conjunction with pre-release SW testing?

===Aurora===
 
===Beta===
 
===Release===
 

== QA ==
===Aurora===
 
===Beta===
QAWANTED ([http://bit.ly/IhfxAz query])
* {{bug|729507}} Crash in JSObject::finish - unable to reproduce crash with Yandex, any other leads we can pursue?

Nightly Betas Proposal
* Daily checkpoint for automation (as we do now with Nightly & Aurora)
* Staggered weekly checkpoint for smoketests, feature sign-offs, and exploratory testing
* Weekly checkpoint for bug fix verification progress, tracking to 0-bugs before release
* Should also do more to encourage a wider dog-fooding audience
* Q) How do we do a dry-run with weekly Betas?

Pre-release Software Proposal
* Current Coverage:
** Marcia dog-foods OSX 10.8 "once in a while", I'm not sure we have anyone doing the same for Win8
** Marcia dog-foods the official Flash Betas when they appear on labs.adobe.com
** Flash is tested every week in our Firefox Beta sign-offs (mostly regression tests against the current Flash release)
* Proposal: treat pre-release OS and Flash as "features"
** If OSX 10.8 is due out around the same time as Firefox 14 (June), add it to the "feature sign-offs" for Firefox 14 (marcia)
** If Win 8 is due out around the same time as Firefox 16 (October), add it to the "feature sign-offs" for Firefox 16 (juanb)
** Adobe puts out weekly sandboxed Betas; once a week we put this through a suite of regression and "feature" tests against the lastest Firefox Beta (ashughes)

== RelEng ==
 
== Marketing/Communications ==
* Metrics update: I think ADUs are back ; to normal.
** only 1.7% off all ADUs from last week 3.9% off of two weeks ago.

 

== Roundtable ==
* Pre-release Flash (and OS) testing

* Mobile Test Drivers (MTD)
** Email sent to all@ and everyone@ netted 45 more testers (41 employee, 4 volunteer)
** Keep encouraging people to test Fennec Native Android - see [[Mobile/Testdrivers_Program/How_To/Test|Testing tasks]]

* Rapid Betas update
** L10n scoping for rapid betas, no blockers there
** How is crashkill/socorro doing?
** Complete report on the implementation to go out next week, we'll review bugs on Tuesday (5/8) in the channel meeting

== Actions ==
 
== Triage ==
=== Aurora Queries ===
* [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=ALL+flag%3Aapproval-mozilla-aurora%3F&order=Bug+Number '''Approval requests''']
* [https://bugzilla.mozilla.org/buglist.cgi?field0-0-0=cf_tracking_firefox{{AURORA_VERSION}}&resolution=---&resolution=DUPLICATE&query_format=advanced&type0-0-0=equals&value0-0-0=%3F&order=Bug%20Number&list_id=1793640 '''Tracking noms''']
* [https://bugzilla.mozilla.org/buglist.cgi?field1-0-0=cf_status_firefox{{AURORA_VERSION}};type0-0-0=equals;value0-0-0=%2B;field0-0-0=cf_tracking_firefox{{AURORA_VERSION}};type1-0-0=notregexp;value1-0-0=%28fixed|wontfix|unaffected|verified%29;order=Bug%20Number '''Unresolved Tracking Bugs for FF{{AURORA_VERSION}}''']

=== Beta Queries ===
* [https://bugzilla.mozilla.org/buglist.cgi?&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=approval-mozilla-beta%3F&order=Bug%20Number '''Approval requests''']
* [https://bugzilla.mozilla.org/buglist.cgi?&field0-0-0=cf_tracking_firefox{{BETA_VERSION}}&type0-0-0=equals&value0-0-0=%3F&order=Bug%20Number '''Tracking noms''']
* [https://bugzilla.mozilla.org/buglist.cgi?field1-0-0=cf_status_firefox{{BETA_VERSION}};type0-0-0=equals;value0-0-0=%2B;field0-0-0=cf_tracking_firefox{{BETA_VERSION}};type1-0-0=notregexp;value1-0-0=%28fixed|wontfix|unaffected|verified%29;order=Bug%20Number '''Unresolved Tracking Bugs for FF{{BETA_VERSION}}''']

Firefox/Channels/Meetings/2012-05-03

2012-05-03T21:00:18Z

Lmesa: /* Marketing/Communications */

<center>[[Firefox/Channels/Meetings/{{#time: Y-m-d | {{SUBPAGENAME}} -1 week}}|« previous week]] | [[Firefox/Channels/Meetings |index]] | [[Firefox/Channels/Meetings/{{#time: Y-m-d | {{SUBPAGENAME}} +1 week}}|next week »]]</center>

'''Channel Meeting Details'''
* Tuesdays and Thursday - 2:00pm PDT, 21:00 UTC
* Mountain View Offices: Warp Core Conference Room
* [irc://irc.mozilla.org/planning irc.mozilla.org #planning] for backchannel

'''Video/Teleconference Details - NEW'''
* 650-903-0800 or 650-215-1282 x92 Conf# '''95312''' (US/INTL)
* 1-800-707-2533 (pin 369) Conf# '''95312''' (US)
* Vidyo Room: Warp Core
* Vidyo [https://v.mozilla.com/flex.html?roomdirect.html&key=UK1zyrd7Vhym Guest URL]

{{Notes}}

__FORCETOC__

== Previous Actions ==
* <strike>Alex - make sure everybody who needs to be around to discuss Flash beta is at our next channel meeting</strike>

== Schedule Update ==
* We are [https://mail.mozilla.com/home/akeybl@mozilla.com/Release%20Management.html?view=month&date=20120503 here] on the schedule - the bugs [https://bugzilla.mozilla.org/buglist.cgi?field0-3-0=cf_status_firefox13;type0-1-0=notequals;value0-4-0=verified;field0-1-0=cf_status_firefox13;field0-0-0=cf_tracking_firefox13;type0-4-0=notequals;value0-3-0=unaffected;query_format=advanced;value0-2-0=fixed;value0-1-0=wontfix;type0-3-0=notequals;field0-2-0=cf_status_firefox13;field0-4-0=cf_status_firefox13;type0-0-0=equals;value0-0-0=%2B;type0-2-0=notequals;list_id=3016729 tracked for FF13] is a fairly manageable burndown list at this point
** Engineers and engineering managers have been notified of outstanding tracked bugs

* Pushed out a new desupport hotfix (20120430.01) to fix over-prompting on Tuesday
* 13.0b1 was unthrottled yesterday
* 3.6 EOL MU have been pushed live and signed off yesterday
* 13.0b2 went out today
* We're shooting for a FN14 beta build #2 on 5/8, Google Play store testing is ongoing

* Tuesday 5/8 is the earliest that we'll go out with automatic updates for FF3.6 to FF12 (bugs incoming)

==Add-ons==
* {{bug|750387}} – consider blocklisting Adobe Reader (10.1.3)

== Stability ==
* Q: How can we start looking at top crash lists for Windows 8 and OS X 10.8 in conjunction with pre-release SW testing?

===Aurora===
 
===Beta===
 
===Release===
 

== QA ==
===Aurora===
 
===Beta===
QAWANTED ([http://bit.ly/IhfxAz query])
* {{bug|729507}} Crash in JSObject::finish - unable to reproduce crash with Yandex, any other leads we can pursue?

Nightly Betas Proposal
* Daily checkpoint for automation (as we do now with Nightly & Aurora)
* Staggered weekly checkpoint for smoketests, feature sign-offs, and exploratory testing
* Weekly checkpoint for bug fix verification progress, tracking to 0-bugs before release
* Should also do more to encourage a wider dog-fooding audience
* Q) How do we do a dry-run with weekly Betas?

Pre-release Software Proposal
* Current Coverage:
** Marcia dog-foods OSX 10.8 "once in a while", I'm not sure we have anyone doing the same for Win8
** Marcia dog-foods the official Flash Betas when they appear on labs.adobe.com
** Flash is tested every week in our Firefox Beta sign-offs (mostly regression tests against the current Flash release)
* Proposal: treat pre-release OS and Flash as "features"
** If OSX 10.8 is due out around the same time as Firefox 14 (June), add it to the "feature sign-offs" for Firefox 14 (marcia)
** If Win 8 is due out around the same time as Firefox 16 (October), add it to the "feature sign-offs" for Firefox 16 (juanb)
** Adobe puts out weekly sandboxed Betas; once a week we put this through a suite of regression and "feature" tests against the lastest Firefox Beta (ashughes)

== RelEng ==
 
== Marketing/Communications ==
* Metrics update: I think ADUs are back to normal.
** only 1.7% off all ADUs from last week

 

== Roundtable ==
* Pre-release Flash (and OS) testing

* Mobile Test Drivers (MTD)
** Email sent to all@ and everyone@ netted 45 more testers (41 employee, 4 volunteer)
** Keep encouraging people to test Fennec Native Android - see [[Mobile/Testdrivers_Program/How_To/Test|Testing tasks]]

* Rapid Betas update
** L10n scoping for rapid betas, no blockers there
** How is crashkill/socorro doing?
** Complete report on the implementation to go out next week, we'll review bugs on Tuesday (5/8) in the channel meeting

== Actions ==
 
== Triage ==
=== Aurora Queries ===
* [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=ALL+flag%3Aapproval-mozilla-aurora%3F&order=Bug+Number '''Approval requests''']
* [https://bugzilla.mozilla.org/buglist.cgi?field0-0-0=cf_tracking_firefox{{AURORA_VERSION}}&resolution=---&resolution=DUPLICATE&query_format=advanced&type0-0-0=equals&value0-0-0=%3F&order=Bug%20Number&list_id=1793640 '''Tracking noms''']
* [https://bugzilla.mozilla.org/buglist.cgi?field1-0-0=cf_status_firefox{{AURORA_VERSION}};type0-0-0=equals;value0-0-0=%2B;field0-0-0=cf_tracking_firefox{{AURORA_VERSION}};type1-0-0=notregexp;value1-0-0=%28fixed|wontfix|unaffected|verified%29;order=Bug%20Number '''Unresolved Tracking Bugs for FF{{AURORA_VERSION}}''']

=== Beta Queries ===
* [https://bugzilla.mozilla.org/buglist.cgi?&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=approval-mozilla-beta%3F&order=Bug%20Number '''Approval requests''']
* [https://bugzilla.mozilla.org/buglist.cgi?&field0-0-0=cf_tracking_firefox{{BETA_VERSION}}&type0-0-0=equals&value0-0-0=%3F&order=Bug%20Number '''Tracking noms''']
* [https://bugzilla.mozilla.org/buglist.cgi?field1-0-0=cf_status_firefox{{BETA_VERSION}};type0-0-0=equals;value0-0-0=%2B;field0-0-0=cf_tracking_firefox{{BETA_VERSION}};type1-0-0=notregexp;value1-0-0=%28fixed|wontfix|unaffected|verified%29;order=Bug%20Number '''Unresolved Tracking Bugs for FF{{BETA_VERSION}}''']

Firefox/Planning/2012-05-02

2012-05-02T18:33:06Z

Lmesa: /* Marketing, Press & Public Reaction */

<center>[[Firefox/Planning/{{#time: Y-m-d | {{SUBPAGENAME}} -1 week}}|« previous week]] | [[Firefox/DeliveryMeetings|index]] | [[Firefox/Planning/{{#time: Y-m-d | {{SUBPAGENAME}} +1 week}}|next week »]]</center>

'''Planning Meeting Details'''
* Wednesdays - 11:00am PDT, 18:00 UTC
* Mountain View Offices: Warp Core Conference Room
* Toronto Offices: Finch Conference Room
* [irc://irc.mozilla.org/planning irc.mozilla.org #planning] for backchannel
* (the [[Platform#Meetings|developer meeting]] takes place on Tuesdays)

'''Video/Teleconference Details - NEW'''
* 650-903-0800 or 650-215-1282 x92 Conf# '''95312''' (US/INTL)
* 1-800-707-2533 (pin 369) Conf# '''95312''' (US)
* Vidyo Room: Warp Core
* Vidyo [https://v.mozilla.com/flex.html?roomdirect.html&key=UK1zyrd7Vhym Guest URL]

{{Notes}}

__FORCETOC__

== Actions from Last Week ==

== Schedule & Progress on [[Releases|Upcoming Releases]] ==
=== Kilimanjaro ===
* There is an App/Site compat effort to ensure content works on the Mozilla platform
** Involvement from business dev, QA, product, engineering, dev evangelism, market insights, press
** Information and details being documented [[Program_Management/Programs/Apps/Site_Compatibility|on the wiki]]
** Lawrence Mandel (lmandel) for questions, to get involved

* Contacts requirement in flux, product discussions ongoing so we can have clarity soon on use-cases.

===Firefox Desktop ===
==== Release (3.6, 12, 10esr) ====
* 12 signed off, updates are unthrottled as of last night
* second round of 3.6 EOL MU prompts go out today ({{bug|750403}})
==== Beta (13) ====
* Still 38 bugs [http://mzl.la/Ka58wg tracking 13+] - if your bug has been fixed & landed, please update the status flags
* 13.0b2 coming on Friday (5/4)

==== Aurora (14) ====
* updates unthrottled last Friday

==== Nightly (15) ====
* Very significant Snappy fix landed this week as part of memshrink that reduces leaks in chrome ({{bug|695480}}). This can also catch leaks from add-ons. It should significantly reduce memory usage and thus cycle-collector pauses, etc.
* 744388 [Page Thumbnails] implement a custom storage, don't use the file cache
* 515785 Use new icons for each task in Win7 Jump list tasks
* 729133 preconnect http sessions before cache lookup
* 539095 Expose high-resolution timing API to web content
* 588683 Implement form attribute

=== Firefox Mobile ===
====Beta Plan====
* 2012-05-08: Go to build
* 2012-05-11: Push to market

==== Aurora (14) ====
* Landing blockers

==== Nightly (15) ====
* New front-end work
** Larry
** Reader mode
** Text selection
** HTML5 context menu

=== Services ===
==== Firefox Sync ====

* [http://bit.ly/AndroidSyncBlockers Android blockers]: 0 beta, 8 release, 2 soft
* Work ramping up on Sign into the browser on desktop.

==== Apps In the Cloud Server ====

=== Add-on SDK ===

Release (1.6 -> Firefox 11, 12)
* All is well

Stabilization (1.7 -> Firefox 12, 13)
* Released 1.7b2 last week no new beta this week
* There will be a 1.7RC1 out this afternoon
* On track to release 15 May 2012

Development (1.8 -> Firefox 13, 14)
* On track to merge to Stabilization 15 May 2012
* [https://github.com/mozilla/addon-sdk/pull/387 HTML l10n has landed in Master] - will ship with 1.8
* At last week's Firefox workweek, Irakli hacked up [https://github.com/Gozala/scratch-kit/ SDK support to Firefox’s Scratchpad editor] via his ‘Scratch-kit’ add-on. It can be difficult to get running right now, but will be easier with a planned Fx bug fix.

===Identity===

* SITB progress at work week!

* Product feedback for Sync:
** Not coupled to SITB. SITB is a different product altogether (mutually exclusive with Sync).
** That also means: no "flag day" for now

===Apps===
* Firefox Desktop 14 (Aurora) - landed
** Looking to back out this functionality - {{bug|750936}}
** Native Install
** Chromeless launch of apps
* Firefox Desktop 15 (Nightly)
** Working on fixing bugs - mostly fit and polish to fit Kilimanjaro requirements
** Defining Hometab promotion of apps
** Defining Newtab launchpad of apps

* Firefox Mobile 15 (Nightly) - in progress
** Work started in Fx14 continues in 15.
** Proposed marketplace bundling with Fennec is an open issue. See {{bug|738545}}

* Apps in the Cloud
** AITC client continues
** AITC Server - Completed

== Feedback Summary ==
=== Desktop ===
Firefox 12 issues summary:

Feedback is consistent with what we expected. We have a 4% increase in issues reported on input compared to the first week of the 11.0 release. This increase appears to be result of a combination of the PDF issue on mac (see bug https://bugzilla.mozilla.org/show_bug.cgi?id=747073), Torbutton drag & drop breakage (see bug https://bugzilla.mozilla.org/show_bug.cgi?id=715885) plus general UI changes to tabs & menus for users upgrading from 3.6. We do have 18 new votes on SUMO for the Gmail chat issue (see https://bugzilla.mozilla.org/show_bug.cgi?id=750389).

FF12 praise summary, down 7% from FF11:

fast:
[http://input.mozilla.org/opinion/2889479]
[http://input.mozilla.org/opinion/2889440]
[http://input.mozilla.org/opinion/2889158]
[http://input.mozilla.org/opinion/2888546]
[http://input.mozilla.org/opinion/2887836]

UI:
[http://input.mozilla.org/opinion/2889231]
[http://input.mozilla.org/opinion/2887260]

tools:
[http://input.mozilla.org/opinion/2888595]

values:
[http://input.mozilla.org/opinion/2887289]

stability:
[http://input.mozilla.org/opinion/2887283]
[http://input.mozilla.org/opinion/2886671]

FF13 beta issues summary:

PDF on Mac
[http://input.mozilla.org/en-US/?product=firefox&sentiment=sad&date_end=2012-05-01&date_start=2012-04-27&version=13.0&q=pdf 96 comments]

Flash/video
[http://input.mozilla.org/en-US/?product=firefox&sentiment=sad&date_end=2012-05-01&date_start=2012-04-27&version=13.0&q=flash 74 comments]
[http://input.mozilla.org/en-US/?product=firefox&sentiment=sad&date_end=2012-05-01&date_start=2012-04-27&version=13.0&q=video 82 comments]

FF13 beta praise summary:

default smooth scrolling, well-liked:
[http://input.mozilla.org/en-US/?product=firefox&sentiment=happy&date_end=&date_start=2012-04-25&version=13.0&q=scroll 96 comments]

tab screen:
[http://input.mozilla.org/opinion/2892220]
[http://input.mozilla.org/opinion/2892180]
[http://input.mozilla.org/opinion/2892157]
[http://input.mozilla.org/opinion/2892072]
[http://input.mozilla.org/opinion/2892018]
[http://input.mozilla.org/opinion/2891978]

new start page:
[http://input.mozilla.org/opinion/2891804]
[http://input.mozilla.org/opinion/2891731]
[http://input.mozilla.org/opinion/2891692]
[http://input.mozilla.org/opinion/2891603]

FF14 aurora issues:

UI:
buttons - http://input.mozilla.org/opinion/2882869
feedback - http://input.mozilla.org/opinion/2882855
padlock - http://input.mozilla.org/opinion/2882840

silverlight crash:
[http://input.mozilla.org/opinion/2894746]
[http://input.mozilla.org/opinion/2887444]
[http://input.mozilla.org/opinion/2883579]

click to play:
http://input.mozilla.org/opinion/2890466

FF14 aurora praise:

Click to play:
http://input.mozilla.org/opinion/2891902

Flash stability:
http://input.mozilla.org/opinion/2890763

autocomplete URLs:
[http://input.mozilla.org/opinion/2885547]
[http://input.mozilla.org/opinion/2885642]
[http://input.mozilla.org/opinion/2884021]

full screen:
[http://input.mozilla.org/opinion/2883416]
[http://input.mozilla.org/opinion/2885966]

download manager:
[http://input.mozilla.org/opinion/2880020]
[http://input.mozilla.org/opinion/2888361]

=== Mobile ===

== UX & User Research ==

=== UX Design ===
This week in Firefox UX
* presentation of what happening from last week's work week: [http://madhava.com/egotism/archive/005060.html blog post], [http://www.slideshare.net/madhava/ux-overview-fxworkweekapril2012 direct link to presentation] (Madhava)
** some good coverage: http://arstechnica.com/business/news/2012/05/new-firefox-design-will-offer-uniform-look-across-desktop-and-mobile.ars
* [android] specs for tablet UI now all translated into bugs! (ibarlow)
* [android] reader mode prototype -- continuing to get more awesome - see here {{bug|696921}} (patryk)
* [sign-in] sign-into-browser prototype from Fx workweek (zhenshuo)
* [metro] detailed designs for app bar variants (every context) being worked on (Yuan)
* kicking off in-depth design for apps in Fx integration; some new-tab changes about to go to UX Nightly (Boriss)

== '''Market Insights''' ==
=== Desktop / Platform ===
==== Google ====
* The Google Security team made a post describing [http://blog.chromium.org/2012/04/fuzzing-for-security.html ClusterFuzz], their cluster of machines that perform 50 million fuzz tests per day on the latest Chromium builds. The entire pipeline from managing test cases to verifying fixes is automated.
* A [http://blog.chromium.org/2012/05/better-code-optimization-decisions-for.html new version] of Google's Javascript engine, V8, features a new algorithm that selects between different optimization approaches, resulting in a 25% improvement in performance on SunSpider tests.
* Google Drive launched, with some initial integration into ChromeOS and with [http://www.wired.com/wiredenterprise/2012/04/google-gdrive-chrome-os/ much more planned]. Initial integration [http://www.chromestory.com/2012/04/google-drive-on-chromebook/ arrived] in the ChromeOS dev channel this week. Google applies all its search tools, [http://googlesystem.blogspot.ca/2012/04/google-drive-goggles.html including image recognition] to data that is uploaded to Drive.
==== Microsoft ====
* Microsoft supported the development of a [http://blogs.msdn.com/b/interoperability/archive/2012/04/26/more-news-from-ms-open-tech-announcing-the-open-source-metro-style-theme.aspx Metro style JQuery theme] for web developers
* Microsoft made significant changes to the [http://windowsteamblog.com/windows_phone/b/wpdev/archive/2012/04/30/four-ways-we-re-improving-marketplace.aspx rules for submitting applications to the Windows 8 Marketplace]
* Rumours published in the New York Times and [http://www.zdnet.com/blog/microsoft/bing-bang-boom-is-microsofts-search-engine-secretly-for-sale/12561 elsewhere] suggested that Microsoft has suggested that Facebook purchase the Bing search engine.
==== Opera ====
* Anne van Kesteren [http://annevankesteren.nl/2012/04/prefixes posted her explanation] of why Opera decided to support some webkit-prefixed CSS properties. The [http://www.webkitbits.com/post/22222538210/why-o-why-thoughts-on-operas-implementation-of-webkit-s WebKitBits blog] had a different impression of what should be done.
==== Privacy ====
* Thomas Roessler of the W3C posted a [http://www.w3.org/QA/2012/04/the_state_of_do_not_track.html good summary] of the current state of the Do Not Track initiative at the W3C, European and US levels.
==== Research In Motion ====
* RIM released their [http://devblog.blackberry.com/2012/05/blackberry-10-webworks-sdk/ WebWorks SDK] for Blackberry 10, which "allows web developers to create first class BlackBerry applications using familiar web technologies such as HTML5, CSS, and JavaScript".
* Sencha performed an [http://www.sencha.com/blog/html5-scorecard-rim-blackberry-playbook-2/#date:17:00 in-depth review] of the HTML5 support on the latest version of the Blackberry playbook, characterizing its support as "excellent".

=== Mobile ===

Summary below, full update [http://irinasandu.com/2012/05/02/android-and-mobile-browsing-insights-week-18/ here] and in your inbox.

* Opera released stats on Opera Mini and Mobile user behaviour
* Preliminary Q1 results place Samsung as top smartphone producer
* Kindle Fire estimated to account for over 50% of US Android-based tablet market
* Rumours about a Facebook phone allegedly produced by HTC surfaced again
* First Intel phone features 1.6 GHz Atom Z2460 single core CPU, 400 MHz PowerVR SGX 540 GPU, 1 GB of RAM
* HTC rumoured to be planning manufacture of own set of ARM-based chipsets
* RIM unveiled developer alpha version of BB OS 10
* Tizen version 1.0 was released in form of source code and SDK
* Canonical rumoured to be planning Ubuntu-based mobile devices
* Usage of TV white spectrum for wireless communications making progress in Cambridge, UK
* The list of IP-related litigations between Apple and Samsung features 50 lawsuits in 10 countries

== Marketing, Press & Public Reaction ==

==== Marketing ====
* starting work on next release blog posts; collateral
* seeing a strong response to 3.6 EOL; looks like we've dropped 10-15% of 3.6 ADUs in the past week.

==== Press ====

*[http://www.h-online.com/security/news/item/Firefox-3-6-x-reaches-end-of-life-1558484.html Firefox 3.6.x reaches end of life] 
*[http://www.pcworld.com/businesscenter/article/254633/firefox_13_beta_gets_a_speed_boost_with_spdy_by_default.html Firefox 13 Beta Gets a Speed Boost with SPDY by Default] 
*[http://www.computerworld.com/s/article/9226787/Mozilla_ponders_major_Firefox_UI_refresh Mozilla ponders major Firefox UI refresh] 
*[http://www.webmonkey.com/2012/05/new-firefox-design-will-offer-uniform-look-across-desktop-and-mobile/ New Firefox Design Will Offer Uniform Look Across Desktop and Mobile] 

 

== Questions, Comments, FYI ==
* Does the backout of apps integration in 14 effect the mozillian preview of Apps?
** Answer: No, it does not. The Mozillian Beta preview of Apps will be supported in Nightly.

== Actions this week ==

Firefox/Planning/2012-05-02

2012-05-02T18:27:31Z

Lmesa: /* Questions, Comments, FYI */

<center>[[Firefox/Planning/{{#time: Y-m-d | {{SUBPAGENAME}} -1 week}}|« previous week]] | [[Firefox/DeliveryMeetings|index]] | [[Firefox/Planning/{{#time: Y-m-d | {{SUBPAGENAME}} +1 week}}|next week »]]</center>

'''Planning Meeting Details'''
* Wednesdays - 11:00am PDT, 18:00 UTC
* Mountain View Offices: Warp Core Conference Room
* Toronto Offices: Finch Conference Room
* [irc://irc.mozilla.org/planning irc.mozilla.org #planning] for backchannel
* (the [[Platform#Meetings|developer meeting]] takes place on Tuesdays)

'''Video/Teleconference Details - NEW'''
* 650-903-0800 or 650-215-1282 x92 Conf# '''95312''' (US/INTL)
* 1-800-707-2533 (pin 369) Conf# '''95312''' (US)
* Vidyo Room: Warp Core
* Vidyo [https://v.mozilla.com/flex.html?roomdirect.html&key=UK1zyrd7Vhym Guest URL]

{{Notes}}

__FORCETOC__

== Actions from Last Week ==

== Schedule & Progress on [[Releases|Upcoming Releases]] ==
=== Kilimanjaro ===
* There is an App/Site compat effort to ensure content works on the Mozilla platform
** Involvement from business dev, QA, product, engineering, dev evangelism, market insights, press
** Information and details being documented [[Program_Management/Programs/Apps/Site_Compatibility|on the wiki]]
** Lawrence Mandel (lmandel) for questions, to get involved

* Contacts requirement in flux, product discussions ongoing so we can have clarity soon on use-cases.

===Firefox Desktop ===
==== Release (3.6, 12, 10esr) ====
* 12 signed off, updates are unthrottled as of last night
* second round of 3.6 EOL MU prompts go out today ({{bug|750403}})
==== Beta (13) ====
* Still 38 bugs [http://mzl.la/Ka58wg tracking 13+] - if your bug has been fixed & landed, please update the status flags
* 13.0b2 coming on Friday (5/4)

==== Aurora (14) ====
* updates unthrottled last Friday

==== Nightly (15) ====
* Very significant Snappy fix landed this week as part of memshrink that reduces leaks in chrome ({{bug|695480}}). This can also catch leaks from add-ons. It should significantly reduce memory usage and thus cycle-collector pauses, etc.
* 744388 [Page Thumbnails] implement a custom storage, don't use the file cache
* 515785 Use new icons for each task in Win7 Jump list tasks
* 729133 preconnect http sessions before cache lookup
* 539095 Expose high-resolution timing API to web content
* 588683 Implement form attribute

=== Firefox Mobile ===
====Beta Plan====
* 2012-05-08: Go to build
* 2012-05-11: Push to market

==== Aurora (14) ====
* Landing blockers

==== Nightly (15) ====
* New front-end work
** Larry
** Reader mode
** Text selection
** HTML5 context menu

=== Services ===
==== Firefox Sync ====

* [http://bit.ly/AndroidSyncBlockers Android blockers]: 0 beta, 8 release, 2 soft
* Work ramping up on Sign into the browser on desktop.

==== Apps In the Cloud Server ====

=== Add-on SDK ===

Release (1.6 -> Firefox 11, 12)
* All is well

Stabilization (1.7 -> Firefox 12, 13)
* Released 1.7b2 last week no new beta this week
* There will be a 1.7RC1 out this afternoon
* On track to release 15 May 2012

Development (1.8 -> Firefox 13, 14)
* On track to merge to Stabilization 15 May 2012
* [https://github.com/mozilla/addon-sdk/pull/387 HTML l10n has landed in Master] - will ship with 1.8
* At last week's Firefox workweek, Irakli hacked up [https://github.com/Gozala/scratch-kit/ SDK support to Firefox’s Scratchpad editor] via his ‘Scratch-kit’ add-on. It can be difficult to get running right now, but will be easier with a planned Fx bug fix.

===Identity===

* SITB progress at work week!

* Product feedback for Sync:
** Not coupled to SITB. SITB is a different product altogether (mutually exclusive with Sync).
** That also means: no "flag day" for now

===Apps===
* Firefox Desktop 14 (Aurora) - landed
** Looking to back out this functionality - {{bug|750936}}
** Native Install
** Chromeless launch of apps
* Firefox Desktop 15 (Nightly)
** Working on fixing bugs - mostly fit and polish to fit Kilimanjaro requirements
** Defining Hometab promotion of apps
** Defining Newtab launchpad of apps

* Firefox Mobile 15 (Nightly) - in progress
** Work started in Fx14 continues in 15.
** Proposed marketplace bundling with Fennec is an open issue. See {{bug|738545}}

* Apps in the Cloud
** AITC client continues
** AITC Server - Completed

== Feedback Summary ==
=== Desktop ===
Firefox 12 issues summary:

Feedback is consistent with what we expected. We have a 4% increase in issues reported on input compared to the first week of the 11.0 release. This increase appears to be result of a combination of the PDF issue on mac (see bug https://bugzilla.mozilla.org/show_bug.cgi?id=747073), Torbutton drag & drop breakage (see bug https://bugzilla.mozilla.org/show_bug.cgi?id=715885) plus general UI changes to tabs & menus for users upgrading from 3.6. We do have 18 new votes on SUMO for the Gmail chat issue (see https://bugzilla.mozilla.org/show_bug.cgi?id=750389).

FF12 praise summary, down 7% from FF11:

fast:
[http://input.mozilla.org/opinion/2889479]
[http://input.mozilla.org/opinion/2889440]
[http://input.mozilla.org/opinion/2889158]
[http://input.mozilla.org/opinion/2888546]
[http://input.mozilla.org/opinion/2887836]

UI:
[http://input.mozilla.org/opinion/2889231]
[http://input.mozilla.org/opinion/2887260]

tools:
[http://input.mozilla.org/opinion/2888595]

values:
[http://input.mozilla.org/opinion/2887289]

stability:
[http://input.mozilla.org/opinion/2887283]
[http://input.mozilla.org/opinion/2886671]

FF13 beta issues summary:

PDF on Mac
[http://input.mozilla.org/en-US/?product=firefox&sentiment=sad&date_end=2012-05-01&date_start=2012-04-27&version=13.0&q=pdf 96 comments]

Flash/video
[http://input.mozilla.org/en-US/?product=firefox&sentiment=sad&date_end=2012-05-01&date_start=2012-04-27&version=13.0&q=flash 74 comments]
[http://input.mozilla.org/en-US/?product=firefox&sentiment=sad&date_end=2012-05-01&date_start=2012-04-27&version=13.0&q=video 82 comments]

FF13 beta praise summary:

default smooth scrolling, well-liked:
[http://input.mozilla.org/en-US/?product=firefox&sentiment=happy&date_end=&date_start=2012-04-25&version=13.0&q=scroll 96 comments]

tab screen:
[http://input.mozilla.org/opinion/2892220]
[http://input.mozilla.org/opinion/2892180]
[http://input.mozilla.org/opinion/2892157]
[http://input.mozilla.org/opinion/2892072]
[http://input.mozilla.org/opinion/2892018]
[http://input.mozilla.org/opinion/2891978]

new start page:
[http://input.mozilla.org/opinion/2891804]
[http://input.mozilla.org/opinion/2891731]
[http://input.mozilla.org/opinion/2891692]
[http://input.mozilla.org/opinion/2891603]

FF14 aurora issues:

UI:
buttons - http://input.mozilla.org/opinion/2882869
feedback - http://input.mozilla.org/opinion/2882855
padlock - http://input.mozilla.org/opinion/2882840

silverlight crash:
[http://input.mozilla.org/opinion/2894746]
[http://input.mozilla.org/opinion/2887444]
[http://input.mozilla.org/opinion/2883579]

click to play:
http://input.mozilla.org/opinion/2890466

FF14 aurora praise:

Click to play:
http://input.mozilla.org/opinion/2891902

Flash stability:
http://input.mozilla.org/opinion/2890763

autocomplete URLs:
[http://input.mozilla.org/opinion/2885547]
[http://input.mozilla.org/opinion/2885642]
[http://input.mozilla.org/opinion/2884021]

full screen:
[http://input.mozilla.org/opinion/2883416]
[http://input.mozilla.org/opinion/2885966]

download manager:
[http://input.mozilla.org/opinion/2880020]
[http://input.mozilla.org/opinion/2888361]

=== Mobile ===

== UX & User Research ==

=== UX Design ===
This week in Firefox UX
* presentation of what happening from last week's work week: [http://madhava.com/egotism/archive/005060.html blog post], [http://www.slideshare.net/madhava/ux-overview-fxworkweekapril2012 direct link to presentation] (Madhava)
** some good coverage: http://arstechnica.com/business/news/2012/05/new-firefox-design-will-offer-uniform-look-across-desktop-and-mobile.ars
* [android] specs for tablet UI now all translated into bugs! (ibarlow)
* [android] reader mode prototype -- continuing to get more awesome - see here {{bug|696921}} (patryk)
* [sign-in] sign-into-browser prototype from Fx workweek (zhenshuo)
* [metro] detailed designs for app bar variants (every context) being worked on (Yuan)
* kicking off in-depth design for apps in Fx integration; some new-tab changes about to go to UX Nightly (Boriss)

== '''Market Insights''' ==
=== Desktop / Platform ===
==== Google ====
* The Google Security team made a post describing [http://blog.chromium.org/2012/04/fuzzing-for-security.html ClusterFuzz], their cluster of machines that perform 50 million fuzz tests per day on the latest Chromium builds. The entire pipeline from managing test cases to verifying fixes is automated.
* A [http://blog.chromium.org/2012/05/better-code-optimization-decisions-for.html new version] of Google's Javascript engine, V8, features a new algorithm that selects between different optimization approaches, resulting in a 25% improvement in performance on SunSpider tests.
* Google Drive launched, with some initial integration into ChromeOS and with [http://www.wired.com/wiredenterprise/2012/04/google-gdrive-chrome-os/ much more planned]. Initial integration [http://www.chromestory.com/2012/04/google-drive-on-chromebook/ arrived] in the ChromeOS dev channel this week. Google applies all its search tools, [http://googlesystem.blogspot.ca/2012/04/google-drive-goggles.html including image recognition] to data that is uploaded to Drive.
==== Microsoft ====
* Microsoft supported the development of a [http://blogs.msdn.com/b/interoperability/archive/2012/04/26/more-news-from-ms-open-tech-announcing-the-open-source-metro-style-theme.aspx Metro style JQuery theme] for web developers
* Microsoft made significant changes to the [http://windowsteamblog.com/windows_phone/b/wpdev/archive/2012/04/30/four-ways-we-re-improving-marketplace.aspx rules for submitting applications to the Windows 8 Marketplace]
* Rumours published in the New York Times and [http://www.zdnet.com/blog/microsoft/bing-bang-boom-is-microsofts-search-engine-secretly-for-sale/12561 elsewhere] suggested that Microsoft has suggested that Facebook purchase the Bing search engine.
==== Opera ====
* Anne van Kesteren [http://annevankesteren.nl/2012/04/prefixes posted her explanation] of why Opera decided to support some webkit-prefixed CSS properties. The [http://www.webkitbits.com/post/22222538210/why-o-why-thoughts-on-operas-implementation-of-webkit-s WebKitBits blog] had a different impression of what should be done.
==== Privacy ====
* Thomas Roessler of the W3C posted a [http://www.w3.org/QA/2012/04/the_state_of_do_not_track.html good summary] of the current state of the Do Not Track initiative at the W3C, European and US levels.
==== Research In Motion ====
* RIM released their [http://devblog.blackberry.com/2012/05/blackberry-10-webworks-sdk/ WebWorks SDK] for Blackberry 10, which "allows web developers to create first class BlackBerry applications using familiar web technologies such as HTML5, CSS, and JavaScript".
* Sencha performed an [http://www.sencha.com/blog/html5-scorecard-rim-blackberry-playbook-2/#date:17:00 in-depth review] of the HTML5 support on the latest version of the Blackberry playbook, characterizing its support as "excellent".

=== Mobile ===

Summary below, full update [http://irinasandu.com/2012/05/02/android-and-mobile-browsing-insights-week-18/ here] and in your inbox.

* Opera released stats on Opera Mini and Mobile user behaviour
* Preliminary Q1 results place Samsung as top smartphone producer
* Kindle Fire estimated to account for over 50% of US Android-based tablet market
* Rumours about a Facebook phone allegedly produced by HTC surfaced again
* First Intel phone features 1.6 GHz Atom Z2460 single core CPU, 400 MHz PowerVR SGX 540 GPU, 1 GB of RAM
* HTC rumoured to be planning manufacture of own set of ARM-based chipsets
* RIM unveiled developer alpha version of BB OS 10
* Tizen version 1.0 was released in form of source code and SDK
* Canonical rumoured to be planning Ubuntu-based mobile devices
* Usage of TV white spectrum for wireless communications making progress in Cambridge, UK
* The list of IP-related litigations between Apple and Samsung features 50 lawsuits in 10 countries

== Marketing, Press & Public Reaction ==

==== Marketing ====
* starting work on next release blog posts; collateral
* seeing a strong response to 3.6 EOL; looks like we've dropped 10-15% ADUs in the past week.

==== Press ====

*[http://www.h-online.com/security/news/item/Firefox-3-6-x-reaches-end-of-life-1558484.html Firefox 3.6.x reaches end of life] 
*[http://www.pcworld.com/businesscenter/article/254633/firefox_13_beta_gets_a_speed_boost_with_spdy_by_default.html Firefox 13 Beta Gets a Speed Boost with SPDY by Default] 
*[http://www.computerworld.com/s/article/9226787/Mozilla_ponders_major_Firefox_UI_refresh Mozilla ponders major Firefox UI refresh] 
*[http://www.webmonkey.com/2012/05/new-firefox-design-will-offer-uniform-look-across-desktop-and-mobile/ New Firefox Design Will Offer Uniform Look Across Desktop and Mobile] 

 

== Questions, Comments, FYI ==
* Does the backout of apps integration in 14 effect the mozillian preview of Apps?
** Answer: No, it does not. The Mozillian Beta preview of Apps will be supported in Nightly.

== Actions this week ==

Firefox/Planning/2012-05-02

2012-05-02T18:10:37Z

Lmesa: /* Marketing */

<center>[[Firefox/Planning/{{#time: Y-m-d | {{SUBPAGENAME}} -1 week}}|« previous week]] | [[Firefox/DeliveryMeetings|index]] | [[Firefox/Planning/{{#time: Y-m-d | {{SUBPAGENAME}} +1 week}}|next week »]]</center>

'''Planning Meeting Details'''
* Wednesdays - 11:00am PDT, 18:00 UTC
* Mountain View Offices: Warp Core Conference Room
* Toronto Offices: Finch Conference Room
* [irc://irc.mozilla.org/planning irc.mozilla.org #planning] for backchannel
* (the [[Platform#Meetings|developer meeting]] takes place on Tuesdays)

'''Video/Teleconference Details - NEW'''
* 650-903-0800 or 650-215-1282 x92 Conf# '''95312''' (US/INTL)
* 1-800-707-2533 (pin 369) Conf# '''95312''' (US)
* Vidyo Room: Warp Core
* Vidyo [https://v.mozilla.com/flex.html?roomdirect.html&key=UK1zyrd7Vhym Guest URL]

{{Notes}}

__FORCETOC__

== Actions from Last Week ==

== Schedule & Progress on [[Releases|Upcoming Releases]] ==
=== Kilimanjaro ===
* There is an App/Site compat effort to ensure content works on the Mozilla platform
** Involvement from business dev, QA, product, engineering, dev evangelism, market insights, press
** Information and details being documented [[Program_Management/Programs/Apps/Site_Compatibility|on the wiki]]
** Lawrence Mandel (lmandel) for questions, to get involved

===Firefox Desktop ===
==== Release (3.6, 12, 10esr) ====
* 12 signed off, updates are unthrottled as of last night
* second round of 3.6 EOL MU prompts go out today ({{bug|750403}})
==== Beta (13) ====
* Still 38 bugs [http://mzl.la/Ka58wg tracking 13+] - if your bug has been fixed & landed, please update the status flags
* 13.0b2 coming on Friday (5/4)

==== Aurora (14) ====
* updates unthrottled last Friday

==== Nightly (15) ====
* Very significant Snappy fix landed this week as part of memshrink that reduces leaks in chrome ({{bug|695480}}). This can also catch leaks from add-ons. It should significantly reduce memory usage and thus cycle-collector pauses, etc.

=== Firefox Mobile ===
====Beta Plan====
* 2012-05-08: Go to build
* 2012-05-11: Push to market

==== Aurora (14) ====
* Landing blockers

==== Nightly (15) ====
* New front-end work
** Larry
** Reader mode
** Text selection
** HTML5 context menu

=== Services ===
==== Firefox Sync ====

* [http://bit.ly/AndroidSyncBlockers Android blockers]: 0 beta, 8 release, 2 soft
* Work ramping up on Sign into the browser on desktop.

==== Apps In the Cloud Server ====

=== Add-on SDK ===

Release (1.6 -> Firefox 11, 12)
* All is well

Stabilization (1.7 -> Firefox 12, 13)
* Released 1.7b2 last week no new beta this week
* There will be a 1.7RC1 out this afternoon
* On track to release 15 May 2012

Development (1.8 -> Firefox 13, 14)
* On track to merge to Stabilization 15 May 2012
* [https://github.com/mozilla/addon-sdk/pull/387 HTML l10n has landed in Master] - will ship with 1.8
* At last week's Firefox workweek, Irakli hacked up [https://github.com/Gozala/scratch-kit/ SDK support to Firefox’s Scratchpad editor] via his ‘Scratch-kit’ add-on. It can be difficult to get running right now, but will be easier with a planned Fx bug fix.

===Identity===

===Apps===
* Firefox Desktop 14 (Aurora) - landed
** Looking to back out this functionality - {{bug|750936}}
** Native Install
** Chromeless launch of apps
* Firefox Desktop 15 (Nightly)
** Working on fixing bugs - mostly fit and polish to fit Kilimanjaro requirements
** Defining Hometab promotion of apps
** Defining Newtab launchpad of apps

* Firefox Mobile 15 (Nightly) - in progress
** Work started in Fx14 continues in 15.
** Proposed marketplace bundling with Fennec is an open issue. See {{bug|738545}}

* Apps in the Cloud
** AITC client continues
** AITC Server - See status above in Services

== Feedback Summary ==
=== Desktop ===
Firefox 12 issues summary:

Feedback is consistent with what we expected. We have a 4% increase in issues reported on input compared to the first week of the 11.0 release. This increase appears to be result of a combination of the PDF issue on mac (see bug https://bugzilla.mozilla.org/show_bug.cgi?id=747073), Torbutton drag & drop breakage (see bug https://bugzilla.mozilla.org/show_bug.cgi?id=715885) plus general UI changes to tabs & menus for users upgrading from 3.6. We do have 18 new votes on SUMO for the Gmail chat issue (see https://bugzilla.mozilla.org/show_bug.cgi?id=750389).

FF12 praise summary, down 7% from FF11:

fast:
[http://input.mozilla.org/opinion/2889479]
[http://input.mozilla.org/opinion/2889440]
[http://input.mozilla.org/opinion/2889158]
[http://input.mozilla.org/opinion/2888546]
[http://input.mozilla.org/opinion/2887836]

UI:
[http://input.mozilla.org/opinion/2889231]
[http://input.mozilla.org/opinion/2887260]

tools:
[http://input.mozilla.org/opinion/2888595]

values:
[http://input.mozilla.org/opinion/2887289]

stability:
[http://input.mozilla.org/opinion/2887283]
[http://input.mozilla.org/opinion/2886671]

FF13 beta issues summary:

PDF on Mac
[http://input.mozilla.org/en-US/?product=firefox&sentiment=sad&date_end=2012-05-01&date_start=2012-04-27&version=13.0&q=pdf 96 comments]

Flash/video
[http://input.mozilla.org/en-US/?product=firefox&sentiment=sad&date_end=2012-05-01&date_start=2012-04-27&version=13.0&q=flash 74 comments]
[http://input.mozilla.org/en-US/?product=firefox&sentiment=sad&date_end=2012-05-01&date_start=2012-04-27&version=13.0&q=video 82 comments]

FF13 beta praise summary:

default smooth scrolling, well-liked:
[http://input.mozilla.org/en-US/?product=firefox&sentiment=happy&date_end=&date_start=2012-04-25&version=13.0&q=scroll 96 comments]

tab screen:
[http://input.mozilla.org/opinion/2892220]
[http://input.mozilla.org/opinion/2892180]
[http://input.mozilla.org/opinion/2892157]
[http://input.mozilla.org/opinion/2892072]
[http://input.mozilla.org/opinion/2892018]
[http://input.mozilla.org/opinion/2891978]

new start page:
[http://input.mozilla.org/opinion/2891804]
[http://input.mozilla.org/opinion/2891731]
[http://input.mozilla.org/opinion/2891692]
[http://input.mozilla.org/opinion/2891603]

FF14 aurora issues:

UI:
buttons - http://input.mozilla.org/opinion/2882869
feedback - http://input.mozilla.org/opinion/2882855
padlock - http://input.mozilla.org/opinion/2882840

silverlight crash:
[http://input.mozilla.org/opinion/2894746]
[http://input.mozilla.org/opinion/2887444]
[http://input.mozilla.org/opinion/2883579]

click to play:
http://input.mozilla.org/opinion/2890466

FF14 aurora praise:

Click to play:
http://input.mozilla.org/opinion/2891902

Flash stability:
http://input.mozilla.org/opinion/2890763

autocomplete URLs:
[http://input.mozilla.org/opinion/2885547]
[http://input.mozilla.org/opinion/2885642]
[http://input.mozilla.org/opinion/2884021]

full screen:
[http://input.mozilla.org/opinion/2883416]
[http://input.mozilla.org/opinion/2885966]

download manager:
[http://input.mozilla.org/opinion/2880020]
[http://input.mozilla.org/opinion/2888361]

=== Mobile ===

== UX & User Research ==

== '''Market Insights''' ==
=== Desktop / Platform ===
==== Google ====
* The Google Security team made a post describing [http://blog.chromium.org/2012/04/fuzzing-for-security.html ClusterFuzz], their cluster of machines that perform 50 million fuzz tests per day on the latest Chromium builds. The entire pipeline from managing test cases to verifying fixes is automated.
* A [http://blog.chromium.org/2012/05/better-code-optimization-decisions-for.html new version] of Google's Javascript engine, V8, features a new algorithm that selects between different optimization approaches, resulting in a 25% improvement in performance on SunSpider tests.
* Google Drive launched, with some initial integration into ChromeOS and with [http://www.wired.com/wiredenterprise/2012/04/google-gdrive-chrome-os/ much more planned]. Initial integration [http://www.chromestory.com/2012/04/google-drive-on-chromebook/ arrived] in the ChromeOS dev channel this week. Google applies all its search tools, [http://googlesystem.blogspot.ca/2012/04/google-drive-goggles.html including image recognition] to data that is uploaded to Drive.
==== Microsoft ====
* Microsoft supported the development of a [http://blogs.msdn.com/b/interoperability/archive/2012/04/26/more-news-from-ms-open-tech-announcing-the-open-source-metro-style-theme.aspx Metro style JQuery theme] for web developers
* Microsoft made significant changes to the [http://windowsteamblog.com/windows_phone/b/wpdev/archive/2012/04/30/four-ways-we-re-improving-marketplace.aspx rules for submitting applications to the Windows 8 Marketplace]
* Rumours published in the New York Times and [http://www.zdnet.com/blog/microsoft/bing-bang-boom-is-microsofts-search-engine-secretly-for-sale/12561 elsewhere] suggested that Microsoft has suggested that Facebook purchase the Bing search engine.
==== Opera ====
* Anne van Kesteren [http://annevankesteren.nl/2012/04/prefixes posted her explanation] of why Opera decided to support some webkit-prefixed CSS properties. The [http://www.webkitbits.com/post/22222538210/why-o-why-thoughts-on-operas-implementation-of-webkit-s WebKitBits blog] had a different impression of what should be done.
==== Privacy ====
* Thomas Roessler of the W3C posted a [http://www.w3.org/QA/2012/04/the_state_of_do_not_track.html good summary] of the current state of the Do Not Track initiative at the W3C, European and US levels.
==== Research In Motion ====
* RIM released their [http://devblog.blackberry.com/2012/05/blackberry-10-webworks-sdk/ WebWorks SDK] for Blackberry 10, which "allows web developers to create first class BlackBerry applications using familiar web technologies such as HTML5, CSS, and JavaScript".
* Sencha performed an [http://www.sencha.com/blog/html5-scorecard-rim-blackberry-playbook-2/#date:17:00 in-depth review] of the HTML5 support on the latest version of the Blackberry playbook, characterizing its support as "excellent".

=== Mobile ===

Summary below, full update [http://irinasandu.com/2012/05/02/android-and-mobile-browsing-insights-week-18/ here] and in your inbox.

* Opera released stats on Opera Mini and Mobile user behaviour
* Preliminary Q1 results place Samsung as top smartphone producer
* Kindle Fire estimated to account for over 50% of US Android-based tablet market
* Rumours about a Facebook phone allegedly produced by HTC surfaced again
* First Intel phone features 1.6 GHz Atom Z2460 single core CPU, 400 MHz PowerVR SGX 540 GPU, 1 GB of RAM
* HTC rumoured to be planning manufacture of own set of ARM-based chipsets
* RIM unveiled developer alpha version of BB OS 10
* Tizen version 1.0 was released in form of source code and SDK
* Canonical rumoured to be planning Ubuntu-based mobile devices
* Usage of TV white spectrum for wireless communications making progress in Cambridge, UK
* The list of IP-related litigations between Apple and Samsung features 50 lawsuits in 10 countries

== Marketing, Press & Public Reaction ==

==== Marketing ====
* starting work on next release blog posts; collateral
* seeing a strong response to 3.6 EOL; looks like we've dropped 10-15% ADUs in the past week.

==== Press ====

*[http://www.h-online.com/security/news/item/Firefox-3-6-x-reaches-end-of-life-1558484.html Firefox 3.6.x reaches end of life] 
*[http://www.pcworld.com/businesscenter/article/254633/firefox_13_beta_gets_a_speed_boost_with_spdy_by_default.html Firefox 13 Beta Gets a Speed Boost with SPDY by Default] 
*[http://www.computerworld.com/s/article/9226787/Mozilla_ponders_major_Firefox_UI_refresh Mozilla ponders major Firefox UI refresh] 
*[http://www.webmonkey.com/2012/05/new-firefox-design-will-offer-uniform-look-across-desktop-and-mobile/ New Firefox Design Will Offer Uniform Look Across Desktop and Mobile] 

 

== Questions, Comments, FYI ==

== Actions this week ==

Firefox/Planning/2012-05-02

2012-05-02T18:06:46Z

Lmesa: /* Marketing, Press & Public Reaction */

<center>[[Firefox/Planning/{{#time: Y-m-d | {{SUBPAGENAME}} -1 week}}|« previous week]] | [[Firefox/DeliveryMeetings|index]] | [[Firefox/Planning/{{#time: Y-m-d | {{SUBPAGENAME}} +1 week}}|next week »]]</center>

'''Planning Meeting Details'''
* Wednesdays - 11:00am PDT, 18:00 UTC
* Mountain View Offices: Warp Core Conference Room
* Toronto Offices: Finch Conference Room
* [irc://irc.mozilla.org/planning irc.mozilla.org #planning] for backchannel
* (the [[Platform#Meetings|developer meeting]] takes place on Tuesdays)

'''Video/Teleconference Details - NEW'''
* 650-903-0800 or 650-215-1282 x92 Conf# '''95312''' (US/INTL)
* 1-800-707-2533 (pin 369) Conf# '''95312''' (US)
* Vidyo Room: Warp Core
* Vidyo [https://v.mozilla.com/flex.html?roomdirect.html&key=UK1zyrd7Vhym Guest URL]

{{Notes}}

__FORCETOC__

== Actions from Last Week ==

== Schedule & Progress on [[Releases|Upcoming Releases]] ==
=== Kilimanjaro ===
* There is an App/Site compat effort to ensure content works on the Mozilla platform
** Involvement from business dev, QA, product, engineering, dev evangelism, market insights, press
** Information and details being documented [[Program_Management/Programs/Apps/Site_Compatibility|on the wiki]]
** Lawrence Mandel (lmandel) for questions, to get involved

===Firefox Desktop ===
==== Release (3.6, 12, 10esr) ====
* 12 signed off, updates are unthrottled as of last night
* second round of 3.6 EOL MU prompts go out today ({{bug|750403}})
==== Beta (13) ====
* Still 38 bugs [http://mzl.la/Ka58wg tracking 13+] - if your bug has been fixed & landed, please update the status flags
* 13.0b2 coming on Friday (5/4)

==== Aurora (14) ====
* updates unthrottled last Friday

==== Nightly (14) ====
* Very significant Snappy fix landed this week as part of memshrink that reduces leaks in chrome ({{bug|695480}}). This can also catch leaks from add-ons. It should significantly reduce memory usage and thus cycle-collector pauses, etc.

=== Firefox Mobile ===
====Beta Plan====
* 2012-05-08: Go to build
* 2012-05-11: Push to market

==== Aurora (14) ====
* Landing blockers

==== Nightly (15) ====
* New front-end work
** Larry
** Reader mode
** Text selection
** HTML5 context menu

=== Services ===
==== Firefox Sync ====

* [http://bit.ly/AndroidSyncBlockers Android blockers]: 0 beta, 8 release, 2 soft
* Work ramping up on Sign into the browser on desktop.

==== Apps In the Cloud Server ====

=== Add-on SDK ===

Release (1.6 -> Firefox 11, 12)
* All is well

Stabilization (1.7 -> Firefox 12, 13)
* Released 1.7b2 last week no new beta this week
* There will be a 1.7RC1 out this afternoon
* On track to release 15 May 2012

Development (1.8 -> Firefox 13, 14)
* On track to merge to Stabilization 15 May 2012
* [https://github.com/mozilla/addon-sdk/pull/387 HTML l10n has landed in Master] - will ship with 1.8
* At last week's Firefox workweek, Irakli hacked up [https://github.com/Gozala/scratch-kit/ SDK support to Firefox’s Scratchpad editor] via his ‘Scratch-kit’ add-on. It can be difficult to get running right now, but will be easier with a planned Fx bug fix.

===Identity===

===Apps===
* Firefox Desktop 14 (Aurora) - landed
** Looking to back out this functionality - {{bug|750936}}
** Native Install
** Chromeless launch of apps
* Firefox Desktop 15 (Nightly)
** Working on fixing bugs - mostly fit and polish to fit Kilimanjaro requirements
** Defining Hometab promotion of apps
** Defining Newtab launchpad of apps

* Firefox Mobile 15 (Nightly) - in progress
** Work started in Fx14 continues in 15.
** Proposed marketplace bundling with Fennec is an open issue. See {{bug|738545}}

* Apps in the Cloud
** AITC client continues
** AITC Server - See status above in Services

== Feedback Summary ==
=== Desktop ===
Firefox 12 issues summary:

Feedback is consistent with what we expected. We have a 4% increase in issues reported on input compared to the first week of the 11.0 release. This increase appears to be result of a combination of the PDF issue on mac (see bug https://bugzilla.mozilla.org/show_bug.cgi?id=747073), Torbutton drag & drop breakage (see bug https://bugzilla.mozilla.org/show_bug.cgi?id=715885) plus general UI changes to tabs & menus for users upgrading from 3.6. We do have 18 new votes on SUMO for the Gmail chat issue (see https://bugzilla.mozilla.org/show_bug.cgi?id=750389).

FF12 praise summary, down 7% from FF11:

fast:
[http://input.mozilla.org/opinion/2889479]
[http://input.mozilla.org/opinion/2889440]
[http://input.mozilla.org/opinion/2889158]
[http://input.mozilla.org/opinion/2888546]
[http://input.mozilla.org/opinion/2887836]

UI:
[http://input.mozilla.org/opinion/2889231]
[http://input.mozilla.org/opinion/2887260]

tools:
[http://input.mozilla.org/opinion/2888595]

values:
[http://input.mozilla.org/opinion/2887289]

stability:
[http://input.mozilla.org/opinion/2887283]
[http://input.mozilla.org/opinion/2886671]

FF13 beta issues summary:

PDF on Mac
[http://input.mozilla.org/en-US/?product=firefox&sentiment=sad&date_end=2012-05-01&date_start=2012-04-27&version=13.0&q=pdf 96 comments]

Flash/video
[http://input.mozilla.org/en-US/?product=firefox&sentiment=sad&date_end=2012-05-01&date_start=2012-04-27&version=13.0&q=flash 74 comments]
[http://input.mozilla.org/en-US/?product=firefox&sentiment=sad&date_end=2012-05-01&date_start=2012-04-27&version=13.0&q=video 82 comments]

FF13 beta praise summary:

default smooth scrolling, well-liked:
[http://input.mozilla.org/en-US/?product=firefox&sentiment=happy&date_end=&date_start=2012-04-25&version=13.0&q=scroll 96 comments]

tab screen:
[http://input.mozilla.org/opinion/2892220]
[http://input.mozilla.org/opinion/2892180]
[http://input.mozilla.org/opinion/2892157]
[http://input.mozilla.org/opinion/2892072]
[http://input.mozilla.org/opinion/2892018]
[http://input.mozilla.org/opinion/2891978]

new start page:
[http://input.mozilla.org/opinion/2891804]
[http://input.mozilla.org/opinion/2891731]
[http://input.mozilla.org/opinion/2891692]
[http://input.mozilla.org/opinion/2891603]

FF14 aurora issues:

UI:
buttons - http://input.mozilla.org/opinion/2882869
feedback - http://input.mozilla.org/opinion/2882855
padlock - http://input.mozilla.org/opinion/2882840

silverlight crash:
[http://input.mozilla.org/opinion/2894746]
[http://input.mozilla.org/opinion/2887444]
[http://input.mozilla.org/opinion/2883579]

click to play:
http://input.mozilla.org/opinion/2890466

FF14 aurora praise:

Click to play:
http://input.mozilla.org/opinion/2891902

Flash stability:
http://input.mozilla.org/opinion/2890763

autocomplete URLs:
[http://input.mozilla.org/opinion/2885547]
[http://input.mozilla.org/opinion/2885642]
[http://input.mozilla.org/opinion/2884021]

full screen:
[http://input.mozilla.org/opinion/2883416]
[http://input.mozilla.org/opinion/2885966]

download manager:
[http://input.mozilla.org/opinion/2880020]
[http://input.mozilla.org/opinion/2888361]

=== Mobile ===

== UX & User Research ==

== '''Market Insights''' ==
=== Desktop / Platform ===
==== Google ====
* The Google Security team made a post describing [http://blog.chromium.org/2012/04/fuzzing-for-security.html ClusterFuzz], their cluster of machines that perform 50 million fuzz tests per day on the latest Chromium builds. The entire pipeline from managing test cases to verifying fixes is automated.
* A [http://blog.chromium.org/2012/05/better-code-optimization-decisions-for.html new version] of Google's Javascript engine, V8, features a new algorithm that selects between different optimization approaches, resulting in a 25% improvement in performance on SunSpider tests.
* Google Drive launched, with some initial integration into ChromeOS and with [http://www.wired.com/wiredenterprise/2012/04/google-gdrive-chrome-os/ much more planned]. Initial integration [http://www.chromestory.com/2012/04/google-drive-on-chromebook/ arrived] in the ChromeOS dev channel this week. Google applies all its search tools, [http://googlesystem.blogspot.ca/2012/04/google-drive-goggles.html including image recognition] to data that is uploaded to Drive.
==== Microsoft ====
* Microsoft supported the development of a [http://blogs.msdn.com/b/interoperability/archive/2012/04/26/more-news-from-ms-open-tech-announcing-the-open-source-metro-style-theme.aspx Metro style JQuery theme] for web developers
* Microsoft made significant changes to the [http://windowsteamblog.com/windows_phone/b/wpdev/archive/2012/04/30/four-ways-we-re-improving-marketplace.aspx rules for submitting applications to the Windows 8 Marketplace]
* Rumours published in the New York Times and [http://www.zdnet.com/blog/microsoft/bing-bang-boom-is-microsofts-search-engine-secretly-for-sale/12561 elsewhere] suggested that Microsoft has suggested that Facebook purchase the Bing search engine.
==== Opera ====
* Anne van Kesteren [http://annevankesteren.nl/2012/04/prefixes posted her explanation] of why Opera decided to support some webkit-prefixed CSS properties. The [http://www.webkitbits.com/post/22222538210/why-o-why-thoughts-on-operas-implementation-of-webkit-s WebKitBits blog] had a different impression of what should be done.
==== Privacy ====
* Thomas Roessler of the W3C posted a [http://www.w3.org/QA/2012/04/the_state_of_do_not_track.html good summary] of the current state of the Do Not Track initiative at the W3C, European and US levels.
==== Research In Motion ====
* RIM released their [http://devblog.blackberry.com/2012/05/blackberry-10-webworks-sdk/ WebWorks SDK] for Blackberry 10, which "allows web developers to create first class BlackBerry applications using familiar web technologies such as HTML5, CSS, and JavaScript".
* Sencha performed an [http://www.sencha.com/blog/html5-scorecard-rim-blackberry-playbook-2/#date:17:00 in-depth review] of the HTML5 support on the latest version of the Blackberry playbook, characterizing its support as "excellent".

=== Mobile ===

Summary below, full update [http://irinasandu.com/2012/05/02/android-and-mobile-browsing-insights-week-18/ here] and in your inbox.

* Opera released stats on Opera Mini and Mobile user behaviour
* Preliminary Q1 results place Samsung as top smartphone producer
* Kindle Fire estimated to account for over 50% of US Android-based tablet market
* Rumours about a Facebook phone allegedly produced by HTC surfaced again
* First Intel phone features 1.6 GHz Atom Z2460 single core CPU, 400 MHz PowerVR SGX 540 GPU, 1 GB of RAM
* HTC rumoured to be planning manufacture of own set of ARM-based chipsets
* RIM unveiled developer alpha version of BB OS 10
* Tizen version 1.0 was released in form of source code and SDK
* Canonical rumoured to be planning Ubuntu-based mobile devices
* Usage of TV white spectrum for wireless communications making progress in Cambridge, UK
* The list of IP-related litigations between Apple and Samsung features 50 lawsuits in 10 countries

== Marketing, Press & Public Reaction ==

==== Marketing ====
* starting work on next release blog posts; collateral

==== Press ====

*[http://www.h-online.com/security/news/item/Firefox-3-6-x-reaches-end-of-life-1558484.html Firefox 3.6.x reaches end of life] 
*[http://www.pcworld.com/businesscenter/article/254633/firefox_13_beta_gets_a_speed_boost_with_spdy_by_default.html Firefox 13 Beta Gets a Speed Boost with SPDY by Default] 
*[http://www.computerworld.com/s/article/9226787/Mozilla_ponders_major_Firefox_UI_refresh Mozilla ponders major Firefox UI refresh] 
*[http://www.webmonkey.com/2012/05/new-firefox-design-will-offer-uniform-look-across-desktop-and-mobile/ New Firefox Design Will Offer Uniform Look Across Desktop and Mobile] 

 

== Questions, Comments, FYI ==

== Actions this week ==

Firefox/Channels/Meetings/2012-05-01

2012-05-01T21:13:08Z

Lmesa: /* Marketing/Communications */

<center>[[Firefox/Channels/Meetings/{{#time: Y-m-d | {{SUBPAGENAME}} -1 week}}|« previous week]] | [[Firefox/Channels/Meetings |index]] | [[Firefox/Channels/Meetings/{{#time: Y-m-d | {{SUBPAGENAME}} +1 week}}|next week »]]</center>

'''Channel Meeting Details'''
* Tuesdays and Thursday - 2:00pm PDT, 21:00 UTC
* Mountain View Offices: Warp Core Conference Room
* [irc://irc.mozilla.org/planning irc.mozilla.org #planning] for backchannel

'''Video/Teleconference Details - NEW'''
* 650-903-0800 or 650-215-1282 x92 Conf# '''95312''' (US/INTL)
* 1-800-707-2533 (pin 369) Conf# '''95312''' (US)
* Vidyo Room: Warp Core
* Vidyo [https://v.mozilla.com/flex.html?roomdirect.html&key=UK1zyrd7Vhym Guest URL]

{{Notes}}

__FORCETOC__

== Previous Actions ==
* Alex - make sure everybody who needs to be around to discuss Flash beta is at our next channel meeting
** reached out to Rob to attend the 5/3 channel meeting

== Schedule Update ==
* We're [https://mail.mozilla.com/home/akeybl@mozilla.com/Release%20Management.html?view=month&date=20120501 here] in the schedule

* Next round of 3.6 EOL Major Update prompts will go out at the earliest today
* Automatic updates from 3.6 to FF12 is planned for the week of 5/7
* FF12 (and associated releases) post-mortem will be held next week

* FF13 beta 2 will go to build today, released Friday (or earlier? Let's discuss in the QA section)

==Add-ons==
* Add-on Hotfix
** {{bug|750832}} – for firefox-hotfix@mozilla.org points to file with Length: 0
* FF12
** {{bug|748269}} – Extension block request: anttoolbar@ant.com
** Blocked on {{bug|750330}} – No new blocklist entries are being published by the API
* FF13
** {{bug|749648}} – startup crash in CheckASLR (mostly correlated to afurladvisor@anchorfree.com add-on)
** Also blocked on {{bug|750330}}
** Can be unblocked once {{bug|749648}} is fixed in FF13 beta 2
* Other
** {{bug|750387}} – consider blocklisting Adobe Reader (10.1.3)

* Random Q: Should we consider shortening the blocklist interval?

== Stability ==

===General===
*{{bug|704158}} - Blocking older versions of Flash.
*{{bug|747847}} - Skype issue
*{{bug|722538}} - Radeon Block
*{{bug|748269}} - Ant block
*{{bug|726425}} - top Flash hang issue. Added some devs to the bug - will try and repro.
*{{bug|744175}} - js Mark issue

===Trunk===
*{{bug|750556}} crash in mozilla::dom::Element::ClearStyleStateLocks

===Aurora===
*{{bug|736695}} - Patch - needs review.
*{{bug|750019}} crash in js::types::TypeSet::addType @ nsIDOMHTMLDocument_Write

===Beta===
*{{bug|749648}} - explosive issue on Beta. Fixed on all branches now.
*{{bug|750625}} crash in nsUrlClassifierPrefixSet::GetPrefixes

== QA ==
===Aurora===
 
nightly hangs on latimes - https://bugzilla.mozilla.org/show_bug.cgi?id=739259

===Beta===
* Q: How about no extended QA sign-offs for Beta 2, only smoke tests and update tests?
** We could focus on frontloading verifications and performing exploratory testing for the rest of the week in parallel
** We can push this off till next Beta if there's any wrinkles in the plan
** Answer: Just give us a timeline and we'll do our best to make that timeline; bare minimum is 24h from builds-in-hand

* The [https://bugzilla.mozilla.org/buglist.cgi?keywords=qawanted%2C%20;keywords_type=allwords;list_id=3000549;field0-0-0=cf_tracking_firefox13;type0-0-1=equals;field0-0-1=cf_tracking_firefox14;query_format=advanced;value0-0-1=%2B;type0-0-0=equals;value0-0-0=%2B qawanted/tracked list] should be cleaned up now, expect more bugs to get the qawanted keyword as Lukas and Alex finish a full pass of the tracking-firefox13+ list

{| class="querytable"
| class="header" | Bug ([http://bit.ly/IhfxAz query])
| class="header" | Status
|-
| {{bug|744175}} Firefox crash @ js::gc::MarkInternal
| Starting investigation (2012-05-01)
|-
| {{bug|750389}} Reports of Gmail Video Chat not working on FF12
| Waiting for Softvision to test (2012-05-01)
|-
| {{bug|744063}} 'Fullscreen playback' NVIDIA stereo 3d for youtube not working in latest Aurora v13
| Waiting for jsmith to test (2012-05-01)
|}

== RelEng ==
* Filed {{bug|750403}} for the next round of EOL prompts, blocked on unthrottling FF12
* {{bug|720822}} – Migrate 3.6 nightly users away from that version/channel before disabling nightlies
* upcoming downtime while moving ftp.m.o/stage/surf to scl3
** RelEng getting access today, will start verification
** needs 5+ hours
** needs tree closure *and* also blocks us doing releases.
*** tinderbox will also be offline during this time
*** possible ride-along moving graphserver

== Marketing/Communications ==
* Need anything from marketing for next 3.6 EOL billboards?
 

== Roundtable ==
* Can we sign off on FF12 unthrottling now that {{bug|748269}} is very close to resolution?
* FF13 beta 1 will not be unthrottled until at least 24 hours after {{bug|750330}} is in place

* See [https://groups.google.com/group/mozilla.dev.planning/browse_thread/thread/5087dece289806bd# this dev-planning thread] for information on the upcoming 'disabled' status flag

* Mobile Test Drivers (MTD)
** Updating all the [https://wiki.mozilla.org/Mobile/Testdrivers_Program/How_To docs]
** Announcement to current mobiletestdrivers list today encouraging them to start testing on Aurora as well as adding new members (staff and volunteer) to the list so be prepared in #mobile for an increase in traffic/questions/bugs as well if you want to help out with mobile test drivers, join #mobiletd

* Rapid Betas update
** This week, we should complete scoping work, begin implementation
** Once scoped, Alex will email the plan to Mozilla community
** Discussions about in-product changes to prevent testing community behavioral changes completed - RS coming back with final word this week
** Rapid Beta l10n conversation happening Thursday morning
** How's the rest of the scoping going?

* Firefox Rewind (tentatively named)
** Rapid Betas are a mid-term goal, Firefox Rewind is long-term
** Feature page still required - basically it's a way for test users to easily roll back to a previous version of Firefox if they tell us why and provide us with their support info
** Discussed at the Firefox team workweek

== Actions ==
* Alex - make sure everybody who needs to be around to discuss Flash beta is at our next channel meeting

== Triage ==
=== Aurora Queries ===
* [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=ALL+flag%3Aapproval-mozilla-aurora%3F&order=Bug+Number '''Approval requests''']
* [https://bugzilla.mozilla.org/buglist.cgi?field0-0-0=cf_tracking_firefox{{AURORA_VERSION}}&resolution=---&resolution=DUPLICATE&query_format=advanced&type0-0-0=equals&value0-0-0=%3F&order=Bug%20Number&list_id=1793640 '''Tracking noms''']
* [https://bugzilla.mozilla.org/buglist.cgi?field1-0-0=cf_status_firefox{{AURORA_VERSION}};type0-0-0=equals;value0-0-0=%2B;field0-0-0=cf_tracking_firefox{{AURORA_VERSION}};type1-0-0=notregexp;value1-0-0=%28fixed|wontfix|unaffected|verified%29;order=Bug%20Number '''Unresolved Tracking Bugs for FF{{AURORA_VERSION}}''']

=== Beta Queries ===
* [https://bugzilla.mozilla.org/buglist.cgi?&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=approval-mozilla-beta%3F&order=Bug%20Number '''Approval requests''']
* [https://bugzilla.mozilla.org/buglist.cgi?&field0-0-0=cf_tracking_firefox{{BETA_VERSION}}&type0-0-0=equals&value0-0-0=%3F&order=Bug%20Number '''Tracking noms''']
* [https://bugzilla.mozilla.org/buglist.cgi?field1-0-0=cf_status_firefox{{BETA_VERSION}};type0-0-0=equals;value0-0-0=%2B;field0-0-0=cf_tracking_firefox{{BETA_VERSION}};type1-0-0=notregexp;value1-0-0=%28fixed|wontfix|unaffected|verified%29;order=Bug%20Number '''Unresolved Tracking Bugs for FF{{BETA_VERSION}}''']

Release Management/Rapid Betas

2012-04-27T23:43:34Z

Lmesa:

Firefox/Channels/Meetings/2012-04-26

2012-04-26T21:07:18Z

Lmesa: /* Marketing/Communications */

Firefox/Planning/2012-04-25

2012-04-25T17:27:00Z

Lmesa: /* Marketing */

MozCampLATAM2012/ProposedTalks/Firefox and the New Release Cycle

2012-04-21T16:18:28Z

Lmesa:

Speaker(s): Laura Mesa & Chris Hofmann

Proposed Track (Engagement & Localization, Technology & Product, Community Building & Collaboration, or BoF): Moving to Rapid Release

Summary: Chris will talk about the reasoning behind the move to rapid release for the first half of the presentation, while Laura will spend the second half talking through the move to feature based releases and what this may look like in practice.

Language in which the talk will be given: English, Spanish slides.

Preferred Day of Talk: Saturday

Presentation Slides (to provide at a later point):

http://dl.dropbox.com/u/37305222/Mozcamp/Laura%20M/mozcamp_BA_2012_FBMktg-eS.pdf
http://dl.dropbox.com/u/37305222/Mozcamp/Laura%20M/mozcamp_BA_2012_FBMktg.ppt.pdf

Ideal Audience Size:

Equipment Needs (Video projector already included):

To Be Completed by the Audience-

Submit a Question for the Speaker(s) here:

Place your name here if you would like to attend this talk:

* mgalli
* Reuben Morais
* Fabricio Zuardi
* Rfuardo Urcullu (Urcu)
* Gloria P. Meneses (Izel)
* Jairo Ruiz (jaruiz33)
* Christiano Alves
* Marcelo Poli
* digitalfredy
* Aldo Medina(Aldopy)

Releases/Firefox 12/Final Signoffs

2012-04-18T19:21:36Z

Lmesa: /* Outstanding Issues/Concerns */

This page will track declaring the latest mozilla-beta build as the final in this cycle and starting the build off of the mozilla-release repository.

'''Please note that issues found in the final moments of the beta period may still require us to rebuild before release'''

== Focus Areas ==
=== Tracking Details ===
 

=== Add-ons ===
==== Current Status ====
 
==== Outstanding Issues/Concerns ====
 

=== Stability ===
==== Current Status ====
 

==== Outstanding Issues/Concerns ====
 

==== Mobile specific stability notes ====
 
=== QA ===
==== Current Status - Desktop ====
 

==== Outstanding Issues/Concerns - Desktop ====
* {{bug|746644}} Massive memory leak when opening web page (thegeekstuff.com) and 'javascript.options.strict' enabled
** Firefox 12 regression from 12.0a1 Nightly 20120112 -- recoverable hang on Mac/Linux, unrecoverable on Windows

==== Current Status - Mobile ====
 

==== Outstanding Issues/Concerns - Mobile ====
 
=== Security ===
==== Current Status ====
 

==== Outstanding Issues ====
 

=== Localization ===
==== Current Status ====
 
==== Outstanding Issues/Concerns ====
 

=== Build Mechanics ===
==== Current Status ====
 
==== Outstanding Issues/Concerns ====
 

=== Web Content ===
==== Current Status ====
* Tracking Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=735322
* Slightly more complicated project than usual as this includes 3.6 EOL pushes and other billboards. Having said that, I think we're very much on schedule for 4/24.
* Jaclyn Fu on point for release on 4/24.

 

==== Outstanding Issues/Concerns ====
* Release Notes and Review of Release Notes

 

=== Services ===
==== Current Status ====
* Good to go
 

==== Outstanding Issues/Concerns ====
* None
 

=== ESR ===
==== Current Status - Desktop ====
 

==== Outstanding Issues/Concerns - Desktop ====
 
==== Current Status - Mobile ====
 

==== Outstanding Issues/Concerns - Mobile ====

Releases/Firefox 12/Final Signoffs

2012-04-18T19:13:20Z

Lmesa: /* Current Status */

This page will track declaring the latest mozilla-beta build as the final in this cycle and starting the build off of the mozilla-release repository.

'''Please note that issues found in the final moments of the beta period may still require us to rebuild before release'''

== Focus Areas ==
=== Tracking Details ===
 

=== Add-ons ===
==== Current Status ====
 
==== Outstanding Issues/Concerns ====
 

=== Stability ===
==== Current Status ====
 

==== Outstanding Issues/Concerns ====
 

==== Mobile specific stability notes ====
 
=== QA ===
==== Current Status - Desktop ====
 

==== Outstanding Issues/Concerns - Desktop ====
* {{bug|746644}} Massive memory leak when opening web page (thegeekstuff.com) and 'javascript.options.strict' enabled
** Firefox 12 regression from 12.0a1 Nightly 20120112 -- recoverable hang on Mac/Linux, unrecoverable on Windows

==== Current Status - Mobile ====
 

==== Outstanding Issues/Concerns - Mobile ====
 
=== Security ===
==== Current Status ====
 

==== Outstanding Issues ====
 

=== Localization ===
==== Current Status ====
 
==== Outstanding Issues/Concerns ====
 

=== Build Mechanics ===
==== Current Status ====
 
==== Outstanding Issues/Concerns ====
 

=== Web Content ===
==== Current Status ====
* Tracking Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=735322
* Slightly more complicated project than usual as this includes 3.6 EOL pushes and other billboards. Having said that, I think we're very much on schedule for 4/24.
* Jaclyn Fu on point for release on 4/24.

 

==== Outstanding Issues/Concerns ====
 

=== Services ===
==== Current Status ====
* Good to go
 

==== Outstanding Issues/Concerns ====
* None
 

=== ESR ===
==== Current Status - Desktop ====
 

==== Outstanding Issues/Concerns - Desktop ====
 
==== Current Status - Mobile ====
 

==== Outstanding Issues/Concerns - Mobile ====

Releases/Firefox 12/Final Signoffs

2012-04-18T19:11:38Z

Lmesa: /* Current Status */

This page will track declaring the latest mozilla-beta build as the final in this cycle and starting the build off of the mozilla-release repository.

'''Please note that issues found in the final moments of the beta period may still require us to rebuild before release'''

== Focus Areas ==
=== Tracking Details ===
 

=== Add-ons ===
==== Current Status ====
 
==== Outstanding Issues/Concerns ====
 

=== Stability ===
==== Current Status ====
 

==== Outstanding Issues/Concerns ====
 

==== Mobile specific stability notes ====
 
=== QA ===
==== Current Status - Desktop ====
 

==== Outstanding Issues/Concerns - Desktop ====
* {{bug|746644}} Massive memory leak when opening web page (thegeekstuff.com) and 'javascript.options.strict' enabled
** Firefox 12 regression from 12.0a1 Nightly 20120112 -- recoverable hang on Mac/Linux, unrecoverable on Windows

==== Current Status - Mobile ====
 

==== Outstanding Issues/Concerns - Mobile ====
 
=== Security ===
==== Current Status ====
 

==== Outstanding Issues ====
 

=== Localization ===
==== Current Status ====
 
==== Outstanding Issues/Concerns ====
 

=== Build Mechanics ===
==== Current Status ====
 
==== Outstanding Issues/Concerns ====
 

=== Web Content ===
==== Current Status ====
* Tracking Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=735322
* Slightly more complicated project than usual as this includes 3.6 EOL pushes and other billboards.

 

==== Outstanding Issues/Concerns ====
 

=== Services ===
==== Current Status ====
* Good to go
 

==== Outstanding Issues/Concerns ====
* None
 

=== ESR ===
==== Current Status - Desktop ====
 

==== Outstanding Issues/Concerns - Desktop ====
 
==== Current Status - Mobile ====
 

==== Outstanding Issues/Concerns - Mobile ====

Firefox/Planning/2012-04-18

2012-04-18T18:28:27Z

Lmesa: /* Marketing, Press & Public Reaction */

Firefox/Planning/2012-04-18

2012-04-18T18:22:30Z

Lmesa: /* Marketing, Press & Public Reaction */

Firefox/Planning/2012-04-18

2012-04-18T18:12:07Z

Lmesa: /* Kilimanjaro */

Firefox/Planning/2012-04-18

2012-04-18T18:11:45Z

Lmesa: /* Kilimanjaro */

Firefox/Planning/2012-04-18

2012-04-18T16:45:40Z

Lmesa: /* Marketing, Press & Public Reaction */

Firefox/Channels/Meetings/2012-04-17

2012-04-17T21:15:24Z

Lmesa: /* Marketing/Communications */