Confirmed users
933
edits
Firefox/Meeting/16-Feb-2016: Difference between revisions
m
fix import formatting
(Import) |
m (fix import formatting) |
||
| Line 1: | Line 1: | ||
== Actions from last meeting == | == Actions from last meeting == | ||
<ul class="bullet"><li>None</li></ul><br> | |||
== General Topics / Roundtable == | |||
(tips/tricks/FYI, productivity improvements, industry news)<br><ul class="bullet"><li>[MattN] mozscreenshots in automation</li><ul class="bullet"><li>https://developer.mozilla.org/en-US/docs/Mozilla/QA/Browser_screenshots</li><li>Preferences and default Devtools are now also captured on Nightlies</li></ul><li>Project ideas and mentors wanted for Summer of Code 2016 & Outreachy</li><li>MozReview can be pushed to with Git: https://mozilla-version-control-tools.readthedocs.org/en/latest/mozreview/install-git.html#mozreview-install-git</li><li>Double-clicking on diffs to open comments in MozReview will be user-optional soon: https://bugzilla.mozilla.org/show_bug.cgi?id=1246769</li><li>rstrong on indefinite leave, ping bsmedberg if you need assistance</li><li>Please consider taking some time this week to doublecheck non-fixed security bugs you have access to, whether they have owners, and are otherwise in a 'good' state.</li><ul class="bullet"><li>Q: is there a way to see how many security/restricted-access bugs there are in a component?</li><ul class="bullet"><li>If you are in the relevant security group for that component, you can bugzilla quicksearch for "group:security" combined with whatever other quicksearch terms for open/closed bugs, components, etc.</li><ul class="bullet"><li>I do not believe there is a way to determine this number if you are not in the relevant security group; if you think you should be in a particular group and aren't, speak to your manager. If you are a volunteer and think you need access, I'm not sure what to do, but you could ping me (Gijs) and I'll find out.</li><li>It may or may not be useful to have counts per component more accessible than they currently are. I'm not the right person to talk to and/or make a decision regarding that, consider talking to Emma Humphries with ideas/thoughts about that.</li></ul></ul></ul></ul><br> | |||
== Friends of the Firefox team == | |||
(Give a shoutout/thanks to people for helping fix and test bugs. Introductions)<br><ul class="bullet"><li>nhnt11 has returned for another internship</li><li>Resolved bugs (excluding employees): http://mzl.la/1oFBiWj</li><ul class="bullet"><li>More than one bug fixed:</li><ul class="bullet"><li>Edouard Oger [:eoger]</li><li>Jeffrey Tran</li><li>Tim Nguyen [:ntim]</li></ul></ul></ul> | |||
== Project Updates == | |||
=== Add-ons === | |||
<ul class="bullet"><li><br></li></ul><br> | |||
=== E10s === | |||
<ul class="bullet"><li>Very few M8's remain. We have a short list of M9's as well (M8 is "things we truly believed we needed to fix for 46", and M9 is "things we discovered needed to be fixed from Telemetry / beta bug reports")</li><li>First Experiment has concluded (e10s enabled on beta for users with and without add-ons)</li><ul class="bullet"><li>Even with add-ons, the main process crashes less when e10s is enabled, which is good</li><li>However, when you sum the number of parent + content process crashes, e10s seems less stable than non-e10s, even for users without add-ons</li><ul class="bullet"><li>https://github.com/vitillo/e10s_analyses/blob/f9ad11ff7fafaf55d8ca740bef660773b7057927/beta45-withaddons/e10s_crash_rate_without_addons.ipynb</li><li>https://github.com/vitillo/e10s_analyses/blob/f9ad11ff7fafaf55d8ca740bef660773b7057927/beta45-withaddons/e10s_crash_rate.ipynb</li><li>https://bugzilla.mozilla.org/show_bug.cgi?id=1246180 has been filed to track stability bugs</li></ul></ul><li>Got some janky add-ons data too: https://gist.github.com/chutten/1c1df7314f480603a6df</li><li>Second Experiment started on Friday</li><ul class="bullet"><li>This is going to blanket a good chunk of our beta population, and is going to be used to inform a go/no-go for e10s on for users without add-ons for Release 46.</li><li>We're also going to make sure our "switching" logic works to ensure that users that aren't supposed to get e10s (have add-ons, a11y stuff), truly don't get it.</li><li>felipe has details</li></ul><li>e10s tests:</li><ul class="bullet"><li>still looking for owners for the long tail</li><li>mochitest-chrome wasn't running at all, a fair bit of work going on there</li></ul></ul><br> | |||
=== Go Faster === | |||
<ul class="bullet"><li><br></li></ul><br> | |||
=== Hello === | |||
<ul class="bullet"><li>The 1.2 release is in-progress</li><ul class="bullet"><li>Working through the release process with Release Management</li></ul></ul><br> | |||
=== Privacy/Security === | |||
<br><ul class="bullet"><li>Working on improvements to malware download prevention and certificate override indication and removal</li></ul><br> | |||
=== Search === | |||
<ul class="bullet"><li>Hijacking remediation: (bug 1203168) Implementing an interstitial prompt to show when searching with a default engine that is suspected of being there due to hijacking: http://i.imgur.com/fivg952.png</li><li>Fixing bugs, with a focus on improving performance.</li></ul><br> | |||
=== Quality of Experience === | |||
<br><ul class="bullet"><li>Still focusing on onboarding work (metabug <strong>1229599</strong>)</li><ul class="bullet"><li>Bookmark menu shows 5 most-recently added bookmarks (1219804)</li><li>show bookmark panel when clicking star (1219794)</li><li>fix Edge bookmarks / readline list import (1229076)</li><li>fix stub installer pinning (1229626)</li><li>when Firefox is your default, check on startup (1189038)</li></ul><li>Created a metabug (1244854) for broader / upcoming QX work</li><li>Mike de Boer moving over from Hello to work on QX</li></ul><br>http://benjamin.smedbergs.us/blog/2012-07-09/using-mercurial-revsets-to-search-for-changes-between-firefox-releases/<br> | |||