26-September-2012

Schedule

Next merge is 2012-10-08

Fx16 betas continue to ship weekly

Major Topics for This Week

ARMv6

Still collecting data to get confidence in the current minimum requirements (800MHz/512MB) as well as look for ways to test devices outside the minimums. We’d like to be able to drop the minimums to get more ARMv6 devices unblocked.

Actions from Last Week

In order to properly assess this issue, it is important to understand the relevant etymology:

“Crapton[ne]” is, obviously, a portmanteau of two words. “Crap” has its origins from the mid-15th century, when crappe was “grain that was trodden underfoot in a barn, chaff”. “Ton”, or in French “tonne”, has its origins in “tun”, a large cask, coming from the old Germanic and Celtic languages of Northern Europe, potentially as far back as the 9th century.

It appears that while “ton” has a much older history, “tonne”, now often used to refer to a metric ton of 1000kg, is in better keeping with Mozilla’s spirit of internationalization and standardization. It is therefore suggested that, for Mozillians, the correct spelling is “craptonne”.

Detailed planning started. The goal is to define and elaborate distinct user groups for Firefox based on a diary study, contextual inquiry and quantitative surveys and analysis. Once established, user groups will be publicly available and employed to make decisions about features and user experience design decisions when resources for a user research study are not available or are unnecessary.

As part of this planning, Leo is starting a quantitative study to identify Firefox user behaviors. Specifically, the project will

Establish a typology of Firefox Users based on Test Pilot data including survey (attitudes) and behaviors

Market Insights

Desktop / Platform

A group of web developers, led by Google, released RoboHornet, a new “benchmark designed around performance pain points real web developers care about”. Microsoft and Mozilla have largely described the suite as a collection of micro-tests inappropriate for overall benchmarking.

Agenda

Note: this meeting is for interactive discussion. Feel free to ask questions!

Friends of the Tree

Thanks to our Friend of the Tree. When adding someone to this section, please get their T-Shirt size, phone number (needed for shipping!) and send it to abourcier@mozilla.com that she can send them a shirt!

Firefox OS

Speaker Location: Dietrich

Lots of finishing moves as we close down the last feature work: FM Radio works, Music can play multiple songs in a row and shuffle and play all, SIM PIN support, can set wallpaper from Homescreen and settings, using default wallpapers or gallery, Email forwarding and reply-all support, default bookmarks available.

19-September-2012

Schedule

Next merge is 2012-10-08

Major Topics for This Week

Vidyo Room Change

Small administrivia. We have an explicit Vidyo room for Mobile now, called… “Mobile”. We’ll be switching to that room for next week’s meeting. Agenda will be updated with the new room and call-in number. We’ll post to newsgroups too.

Bug 730330 – input type=’date/time’ should use the system date/time picker

‘This week’

Bug 789041 – Expose some more JNI to JS

Bug 787765 – Retheme about:home thumbnails

MBrubeck

Metro stuff

Scott (jwir3)

Last Week:

Developed a demo video for reflow-on-zoom. It’s available at: refloz.ogv (Also, there’s an apk build at the same location: refloz.apk – It also has the maxRatio preference available, too. If you choose to try it out, keep in mind it’s still pretty rough.)

Worked on bug 784375: Add ability to specify a maximum font inflation ratio. It’s in review, but I’m trying to get it to reflow when prefs change.

Isolated behavior for -webkit-text-size-adjust: percentage%. It appears to simply increase the specified font size. Still performing a few more tests before adding it to the spec-in-progress for this feature.

This Week:

Still working to fix quirks in reflow-on-zoom prototype.

Assisting mbrubeck in debugging issues with bug 716575 where patch 3 of the series is crashing talos (on apparently an NS_SUCCEEDED(xxx) operation?!?!) We’re not entirely sure how to reproduce- it seems to only happen in Talos tests (mochitests and reftests pass just fine…) I’m going to try and see if I can get talos running on my phone to see if I can shed some light on this problem. We don’t have any information from logs, because when it crashes on talos, we don’t even get a browser_output.txt file. 😐

Firefox 16.0 Beta
Please read the New and Improved Report Here. This allows you to view past information, track trends, etc. We have also started to track Input for Negative trends. We are still expanding this report and thank you for all your feedback so far! Any other feedback please shoot Tyler an Email. Expect this to grow and refine for the next couple of weeks as we improve our reporting tools before Firefox 16 is released.

Some Upcoming Plans are:

Better Tagging for Input

Graph of Input tags allowing us to track trends

SUMO Reported Bugs per release

Positive Input

And your Feedback!

ARMv6
So far we have 3 ARMv6 devices on Input that users are telling us have problems:

LGL45C: Crashes

LG-VM701: Slow to Load

LGL55C: Video Playback is slow

Nexus 7
The big crashing Device on Input is the Nexus 7, do we have a bug on file for this device crashing alot?

Browsers

Google

Google announced that they were dropping support for Internet Explorer 8 from all their web services, as of November 15. Some analysts have interpreted this move as a “bald attempt to get them to switch browsers to Google’s Chrome”.

Extensions Compatibility Tracking

We’ve had reports of some extensions shipped by default (among them CZ) not being compatible with SM 2.12. InvisibleSmiley guesses we missed to version bump them so people with compatible-by-default pref’ed off run into issues now.

Potentially added to Release Train notes to bump the versions on the extensions we ship as standard?

Our build team (Serge, Callek, ewong) needs to automate DOMI branch selection rather than having to tweak the client.py every 6 weeks. bug 763506

sgautherie thinks that the current DOMi branches/tags are not suitable for automatic SeaMonkey branch selection.

Need some traction on this. IanN spoke to Serge at MozCampEU. Serge is waiting for Callek/ewong to agree what needs to happen and to say what is workable or not.

2.x (Last, Current, Next)

2.12 had ~70,900 ADU by last Tuesday and 2.12.1 ~33,000 downloads so far.

Of the released versions, as of last Tuesday, we have 11.3% on 2.0, 3.4% on 2.1-2.3, 4.3% on 2.4-2.6, 1.9% on 2.7, 2.2% on 2.8, 3.7% on 2.9, 3.4% on 2.10, 16.0% on 2.11 and 53.8% on 2.12. So, in the last four weeks, ~0.6k (an additional 0.5% of ADU) have migrated to 2.7 or above.

ADUs continue increasing after the summer dip (up from ~126k and now at ~132k). Still not back up to June levels yet (~144k).

Some people cannot upgrade due to system requirements (OS version, processor capabilities etc.). This even more applies to 2.10 which dropped support for Win2k and WinXP without SP2.

We now have a webpage for latest builds available for “Legacy Platforms” like PPC (bug 759315) but hikerbiker suggests making the Legacy/PPC link more discoverable (Mozillazine post). IanN agrees that the current link is not easily found. InvisibleSmiley said that he didn’t want it to be too obvious or highlighted. IanN thinks splitting and renaming Old to Previous isn’t a bad idea and moving Unofficial Releases after it. Perhaps merging Contributed builds into it.

This is now bug 788543 SeaMonkey – PPC Legacy links are not easy to find.

2.12

2.1 through 2.7 have NOT included the ka (Kartvelian aka Georgian) locale. The last release with ka locale shipped was 2.0.14 and the ka l10n maintainers have not yet updated for changes in later SeaMonkey versions.

The plan was that Callek needs to morph bug 667147 into removing |ka| from our [current] automation entirely (all-locales), and will look at the best locale to transition any ka users to.

The ka owner came back with a bundle of l10n changes to get checked in. Callek to look into doing that, and try to identify if ka will be sustained going forward before completely abandoning. [Needs update from Callek]

Any other business?

Tonymec confirmes that this is scheduled for the weekend before the fall equinox (Friday 21st to Sunday 23rd September). An announcement has been made (shortly after the next to last meeting).

A repeat announcement was sent yesterday to mozilla.dev.apps.seamonkey & the Members List.

Geolocation

Geolocation now works out of the box. MoCo turned it on by default for all applications that build off mozilla-central.

For comm-beta all we need to do is (bug 494421) to add pref("geo.wifi.uri", "https://www.google.com/loc/json"); to browser-prefs.js. However we’re not even sure we are legally allowed to ship with the URL in, we might need to actually put in a pref to disable that in newer builds.

No news to date. Callek will have to reach out to his MoCo legal contact again soonish.

Serge says that on Linux and MacOSX, he just needs someone to actually run the tests and report what they see (screen, console, etc). For example, there is a Mac test about Ctrl+W not working. This should be so trivial.

tonymec suggests that any enthusiastic user, even non-technical, should be able to do some testing (litmus?) and not be scared by technical language and such.

IanN suggests reaching out to the user community using the newsgroups and forums.

Serge to do a write up and send it to Ratty to propagate to the community.

Agenda

Note: this meeting is for interactive discussion. Feel free to ask questions!

Friends of the Tree

Thanks to our Friend of the Tree. When adding someone to this section, please get their T-Shirt size, phone number (needed for shipping!) and send it to abourcier@mozilla.com that she can send them a shirt!

TB 15.0.1 support report – looked at all the topics on September 11th and 1/3 of the topics on Saturday and Sunday – no new major problems discovered other than:

Exchange 2007/2010 Calendar and Tasks Provider not working with Thunderbird 15 [GS], [bug report 132 – experimental version available in bug 132 – WORKAROUND – get it from github: “In branch e4xReplacement in the github repository (https://github.com/1stsetup/exchangecalendar) you can follow the progress.”

How do we make the discussions on tb-planning into concrete actions and documentation on consensus?

If we need a mechanism, we can put that in place, but it’s good if we don’t have to do that.

If we are not able to get some consensus decisions, tb-staff can step up, but hopefully hopefully the community will be able to do that.

Rkent is concerned about the governance model

JB is open to suggestions on other models.

Rkent suggests a council similar to the Seamonkey council.

Ludo suggests rkent as a benevilant dictator

Rkent is concerned about monetisation of Thunderbird in the long run in order to allow people to make a living out of it.

JB is not convinced that we need a board/council for Thunderbird. At least for the first releases he thinks the current model will work.

Mozilla will not allow selling the product, but are happy to see people making money about addons and similar initiatives. Anne-marie is looking into monitisation opportunities that work together with the governance model and Mozilla’s goals.

Rkent asks how can we maintain the backend in case people are mainly working on addons? * The product needs the maintainership and development.

Conclusion is that we need to wait and see how the current model will work for at least a release or two.

We expect some riskier than normal Win8 fixes – QA will be highly engaged

Release of FF16 is on 10/9

CTP blocklisting expected to land on Aurora 17 this week

Firefox OS

All teams focusing on freezing feature work by 9/28 in order to stabilize and close down V1. Product and Engineering management working on a post-9/28 schedule and strategy to drive feature work and blockers to zero.

bug 756140 – even though this is with Cynogenmod, the number of crashes for this is huge (6240 crashes in 3 days) versus the next one down which is 1,576 crashes in 3 days. It’s the biggest crash in 15/16

bug 791462 – is being looked into. It’s causing a spike in the crashing for nightly. It’s a crash in Ion Monkey. Thanks, Marty!