Canmove, confirm
432
edits
Changes
→next meeting: Add 2/20
= next meeting =
([https://fx-team.etherpad.mozilla.org/australis-meeting-notes next meeting has not yet occurred])
=2/20/2014=
* GIF du jour: http://i.imgur.com/Qp2pYXb.gif
* We are in the 3rd week of this release cycle.
** Whoaaa
*** Bugs are basically down ~10 from week 0? :-(
* Backout branch status
** [mconley] Just noticed some intermittent oranges on Holly that don't appear to have been filed on Bugzilla... will file those after this meeting.
* Misc. Australis bugfixing
** Customization mode smoothness
*** Updated CART has been deployed on mozilla-inbound.
*** I've gotten great help from jrmuizel and ehsan on this.
*** The profile JSON file format has changed, so I had to write a new tool to extract interesting samples from a saved profile. This is helping out a lot.
*** I'm filing a lot of "somewhat low hanging fruit", and then trying to determine what the best things are to invest time in.
*** One thing to note is that with gfx.direct2d.disabled, the transition is quite a bit smoother.
**** Bug 974607 - Don't use subpixel aa w/D2D on transparent surfaces if possible
*** The transitionfinished handler in the tabbrowser binding is causing layout flush:
**** Bug 975009 - Make tabbrowser.xml stop causing reflows during the customize mode transition
*** The AeroPeek feature (WindowsPreviewsPerTab.jsm) is trying to get a snapshot after MozAfterPaint is fired:
**** Bug 974507 - Disable WindowsPreviewPerTab during customize mode transition
*** Box-shadows and borders with radii > 0 are expensive to paint
**** Bug 962640 - Temporarily reduce the number of box shadows during customization transition
***** I thought the glass fog was causing most of this, but it's only a small fraction of it, it seems.
**** Bug 974561 - Reduce number of things using border-radius during customize mode transition
*** A recent profile suggests the following division of jank responsibility:
**** It's split pretty evenly.
**** http://people.mozilla.org/~bgirard/cleopatra/#report=18f3ac316abc14da47d6fe1107209187be77cb8a
**** Over 3 opens of the cmode
***** layout: 242 samples
***** paint: 267 samples
* Bug tracking (since last meeting)
** Make sure you do your Aurora uplifts: http://mzl.la/1c11Zb4
** Make sure you ask for approval: http://mzl.la/1j8oUqe
** https://docs.google.com/a/mozilla.com/spreadsheet/ccc?key=0AiPXmmKgSs8udHgzcEhqd0tkTXlJRU8zcXFzMEhneHc
** Bugs fixed within the last week: http://mzl.la/1cmOKRe
** Graph of bugs fixed over time (date adjustable): http://people.mozilla.org/~jwein/australis/bug-tracking.html
** Fixes and reviews over last week:
*** gijs - 7 fixed, 6 reviewed
*** jaws - 5 fixed, 6 reviewed
*** deboer - 3 fixed, 2 reviewed
*** dao - 2 fixed, 6 reviewed
*** conley - 1 fixed, 3 reviewed
*** blair - 0 fixed, 4 reviewed
*** mattn - 0 fixed, 1 reviewed
*** dolske - 0 fixed, 0 reviewed
* Action Items (Last Week)
**
* Roundtable
** Did anyone get an email to book travel for work week?
*** Nope! But I was wondering the same.
** addon-compat bugs...
*** A cluster of 10-15ish unprioritized bugs, what to do?
**** loop in addon authors as soon as possible
**** prioritize investigation if we think it's a big problem or likely to be an Australis bug
*** How to track bugs that end up not being Australis bugs?
**** Not going to track, mark individual bugs as [Australis:P-]
**** Keep them blocking the addon-compat bug (bug 942157) so we can still have a way to track them (ie, "state of known addon compatability for Australis") when we want to look.
* Action Items (New)
**
=2/13/2014=
