canmove, Confirmed users
432
edits
Firefox/Australis Meeting Notes: Difference between revisions
→next meeting: Add 8/15 and 8/22 meetings
(→next meeting: Add 8/15 and 8/22 meetings) |
|||
| Line 4: | Line 4: | ||
= next meeting = | = next meeting = | ||
([https://fx-team.etherpad.mozilla.org/australis-meeting-notes next meeting has not yet occurred]) | ([https://fx-team.etherpad.mozilla.org/australis-meeting-notes next meeting has not yet occurred]) | ||
=8/22/2013= | |||
* Milestone 8, still | |||
** http://i.imgur.com/fVwxoCf.gif | |||
* Perf regression and other landing blockers | |||
** bug 889758 (tpaint regression) | |||
*** ~1.6% on Windows XP PGO | |||
** bug 880611 (ts_paint regression) | |||
*** ~1% for Windows XP NonPGO/PGO | |||
*** vladan is helping by profiling using xperf | |||
** bug 902024 (TART regression) | |||
*** Getting help from avih and graphics on finding the bottlenecks and figuring out what the slow things are | |||
**** Bug 907426 - CreateSimilarSurface allocates a DDB win32 surface (https://bugzilla.mozilla.org/show_bug.cgi?id=907426) | |||
**** Bug 907546 - Avoid DC readback on windows at all cost. (https://bugzilla.mozilla.org/show_bug.cgi?id=907546) | |||
** regression data: https://docs.google.com/spreadsheet/ccc?key=0Asj8iLTl0K0UdDcxemJEWVVXWTlKek1wR09iS2FsOXc#gid=0 | |||
* Bug tracking | |||
** 8/8 to 8/15: P1, P2, P3 ( / / ) | |||
* Roundtable | |||
** AUSTRALMAGATION: http://cl.ly/image/2D0r1p2Y3W3Y | |||
*** :| (:-\) (o_O) (ಠ_ಠ) | |||
*** Possible as a Plan B (landing customization changes without tab changes), but won't pursue unless fixing TART pref regression turns out to take a very very long time. | |||
** Bug 887951 is where we're changing the tooltip of the menu button | |||
*** Matej wants to know what we're calling the thing. Who do we ask about that? | |||
**** "Menu button" | |||
** Character encoding widget has landed! mikedeboer/dao/Gijs++ | |||
** Blogging about Australis?! When/who/what? Rumours keep flying about and I think the sooner we debunk some of them and give a factual overview of what we're planning, the better. | |||
*** what aspect of it? the schedule? I (madhava) have the post that we were going to publish when we land in nightly... | |||
**** More or less: what we have/will change, what we won't change (e.g. persistent rumours we'll kill the bookmarks toolbar / third party toolbars). Schedule I'm less concerned on but is also an aspect. Add-on impact is another. An overview of "what motivates all these changes / what's the unifying motivation of them" is another. I'm not sure 1 blogpost in 1 place is the best thing to cover all these aspects. | |||
*** Madhava has pending post to set initial context for when Australis lands (which will be the first time lots of people will have heard of it or have a chance to try it out). Hard to address things when missing broader context, and the potential audience is pretty small still. | |||
** UX is on mxr: https://mxr.mozilla.org/projects-central/search?find=/ux/&string= | |||
*** rooted at http://mxr.mozilla.org/projects-central/source/ux/ | |||
* Action Items (Last Week) | |||
** None | |||
* Action Items (New) | |||
** (mconley) Push on getting TART landed on test infrastructure | |||
*** Currently that's 2 weeks, but can we make it faster? | |||
** (mconley) Talk to perf team on how we can set a target for us to shoot for. We need a treshold to aim for, otherwise we won't know when we're done. This is absolutely critical. | |||
** (mconley) Before the test lands on talos, how do we measure so that we can work effectively while waiting for the test to land | |||
*** Can we be sure that these numbers scale across platforms? Will a relative improvement / regression on one platform match to another platform? | |||
*** In the event that we show no regression against m-c when the test lands, Australis aside, what's the plan for detecting regressions on low-end hardware? Do we get some low-end hardware into the test machine pool? | |||
** (dolske) mull over what/if we should do a broader post/update on current Australis status | |||
** (madhava) to comment in 887951 about menu button tooltip | |||
=8/15/2013= | |||
* Milestone 8, still | |||
** http://i.imgur.com/zxHLr2e.gif | |||
* Perf regression and other landing blockers | |||
** bug 889758 (tpaint regression) | |||
*** [mconley] Still plugging away hard at this. We're off by ~3ms, and we have some ideas on how to reduce the number of reflows that we hit on window open, but it's slow going and complex. | |||
**** We've been reaching out to graphics and layout for help / tips / guidance (bug 902857) | |||
** bug 880611 (ts_paint regression) | |||
** bug 902024 (TART regression) | |||
*** MattN has an idea on how to possibly drop the regression down by 10% (I believe this is to remove the clip path from the new tab button) | |||
** regression data: https://docs.google.com/spreadsheet/ccc?key=0Asj8iLTl0K0UdDcxemJEWVVXWTlKek1wR09iS2FsOXc#gid=0 | |||
* Bug tracking | |||
** 8/8 to 8/15: P1, P2, P3 ( / / ) | |||
* Roundtable | |||
** Character encoding question | |||
*** Instead of enforcing allowedAreaTypes, we're going to just keep the character encoding widget enabled, even for the case where everything inside it is disabled. That's a rare case, and acceptable. \o/ | |||
** Jared is going to set a min-width on the browser window. This *might* give us a perf win, if coupled with a patch that stops us from checking if the tabstrip is overflowed with 1 tab. Bug 897160. | |||
** Dao landed the Exit button patch today (bug 871203) | |||
* Action Items (Last Week) | |||
** | |||
* Action Items (New) | |||
** | |||
=8/8/2013= | =8/8/2013= | ||