Platform/2010-08-03: Difference between revisions

← Older edit

Platform/2010-08-03 (view source)

Revision as of 00:00, 4 August 2010

4,202 bytes added , 4 August 2010

→‎Roundtable

Joduinn

Confirmed users

2,679

edits

@@ Line 1: / Line 1: @@
 <small>[[Platform/2010-07-27|&laquo; previous week]] | [[Platform|index]] | [[Platform/2010-08-10|next week &raquo;]]</small>
+= Announcements =
+* Focus on blockers
+* Do not check in performance regressions
 = Notices / Schedule =
 '''Previous release post-mortems'''
 * Firefox 3.6.7/8: 2010-08-03 @ 1:00 pm PST, duration 45 mins
+** [https://wiki.mozilla.org/Releases/Post-mortems/Firefox_3.6.7 details are here]
 * Firefox 3.6.4/6: 2010-08-10 @ 1:00 pm PST, duration 1 hour
+** The details on how the post-mortem will be run will be sent out today
 '''Firefox (Supported Branches)'''
@@ Line 12: / Line 19: @@
 '''Firefox (Beta)'''
 * missed code freeze for Firefox 4 Beta 3 due to leaks in Firefox Sync
-* [https://bugzilla.mozilla.org/buglist.cgi?type0-1-0=changedafter&field0-1-0=cf_blocking_20&field0-0-0=cf_blocking_20&resolution=---&chfield=cf_blocking_20&query_format=advanced&value0-1-0=2010-07-30&type0-0-0=changedfrom&value0-0-0=beta3%2B 23 blockers] changed from beta3+ to another milestone after July 30 - this isn't sustainable
+** [https://bugzilla.mozilla.org/buglist.cgi?type0-1-0=changedafter&field0-1-0=cf_blocking_20&field0-0-0=cf_blocking_20&resolution=---&chfield=cf_blocking_20&query_format=advanced&value0-1-0=2010-07-30&type0-0-0=changedfrom&value0-0-0=beta3%2B 23 blockers] changed from beta3+ to another milestone after July 30 - this isn't a sustainable pattern
 ** the [https://bugzilla.mozilla.org/buglist.cgi?resolution=FIXED,VERIFIED&chfieldfrom=2010-07-20%2015%3A00&chfield=resolution&query_format=advanced&chfieldto=2010-08-03%203%3A00&product=Core&product=Firefox&product=NSPR&product=NSS&product=Toolkit complete changelist for this beta]
+'''Firefox mobile (alpha)'''
+* aiming for code freeze on 8/10.
+* [http://bit.ly/cvWLkM Bug list]
 = Blocker Report =
 '''Firefox 3.6.9'''
-* There are [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=ALL%20blocking1.9.2:.9%2B%20-status1.9.2:.9-fixed&order=map_assigned_to.login_name,bugs.bug_id 22 open blockers]
+* There are [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=ALL%20blocking1.9.2:.9%2B%20-status1.9.2:.9-fixed&order=map_assigned_to.login_name,bugs.bug_id 22 open blockers] (+0 w/w)
 ** Code freeze is currently scheduled for Thursday August 12 @ 11:59 pm PST
 ** Let's try to not get them all in on the last day. I'll be bugging people furiously this week and the start of next
+* Only approving blockers at this point
 '''Firefox 3.5.12'''
-* There are [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=ALL%20blocking1.9.1:.12%2B%20-status1.9.1:.12-fixed&order=map_assigned_to.login_name,bugs.bug_id 13 open blockers]
+* There are [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=ALL%20blocking1.9.1:.12%2B%20-status1.9.1:.12-fixed&order=map_assigned_to.login_name,bugs.bug_id 13 open blockers] (+0 w/w)
 * Code freeze is tied to 3.6.9
 '''Firefox 4 Beta'''
 * a handy list of [[Firefox/4/Triage|triage queries]] is available for all!
-** Beta 3: [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=blocking2.0%3Abeta3 35 blockers]
+** Beta 4: [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=blocking2.0%3Abeta4 34 blockers]
-** Beta N: [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=blocking2.0%3AbetaN 132 blockers]
+** Beta N: [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=blocking2.0%3AbetaN 204 blockers]
-** Final: [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=blocking2.0%3Afinal 218 blockers]
+** Final: [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=blocking2.0%3Abeta,final 222 blockers] (462 total)
-** nominations: <font color="red">'''[https://bugzilla.mozilla.org/buglist.cgi?quicksearch=ALL%20blocking2.0%3A%22%3F%22 500+ nominations]'''</font>
+** nominations: [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=ALL%20blocking2.0%3A%22%3F%22 462 nominations] (248 OPEN)
-= Browser / Front End =
-johnath at BlackHat this week, frontend [[Firefox/Goals/2010Q3#Firefox_Development|Q3 Goals]] updated with team status.
 = Firefox Development =
@@ Line 42: / Line 50: @@
 = Platform =
+== GFX ==
+* Going to make enabling Direct2D a Beta 4 blocker, with the aim of blocking beta 5 on hardware accelerated layers (D3D9/OpenGL).
+* Direct2D gradient issues from last week are resolved.
+* libjpeg-turbo integration shows up to 2.5x (+?) speedups of the JPEG decoding code. {{bug|573948}} (jlebar)
+== JS ==
+* JS [http://blog.mozilla.com/rob-sayre/2010/08/02/mozillas-new-javascript-value-representation/ fatvals] landed
+* ES5
+** Landings
+*** {{bug|562448|<code>Function.prototype.apply</code> updated to accept any vaguely array-looking arguments}}, not just arrays or arguments alone
+*** Back to {{bug|531675|ignoring a second argument to <code>eval</code>}}
+*** Changes/refactoring of <code>parseInt</code> in {{bug|577536}}, but after further discussion the one semantic change has been reversed in {{bug|583925}} (now back to status quo, but refactorings remain)
+*** We now {{bug|582643|reject "0x" as valid numeric-literal syntax}} (an ancient bug)
+** Current work
+*** Making getter/setter syntax require an exact number of arguments (zero/one) in {{bug|536472}}
+*** Adding {{bug|514581|poison-pill properties}} for <code>Function.prototype.caller</code> and <code>Function.prototype.arguments</code> when the function in question is a strict-mode function; doing likewise for <code>arguments.caller</code> and <code>arguments.callee</code> in {{bug|514563}} shortly after
+== Layout ==
+* Retained layers
+** The most obvious retained-layers regressions fixed for beta3
+** Regression involving invalidation during reflow: may need to implement display-list-based invalidation for reflow to fix cleanly (brings perf wins too)
+* Content/chrome rendering integration
+** Timothy needs help
+* -moz-font-feature-settings has landed ("Land CSS control of lowlevel font features" done)
+** Needs Harfbuzz enabled to work
+== Video ==
+* Improved software scaling ready to land
+* Standards compliance fixes
+** 'autobuffer' -> 'preload'
+** New load algorithm
 = Windows 7 Test Status  =
+* Same remaining bugs as last week
+* 2 out of 10 test suites with oranges
+* The following bugs had no activity: {{bug|562955}} (jimm) and {{bug|581734}} (no one - smontagu suggested)
+* We also have {{bug|582315}} (felipe)
 = Tree Management =
 = Roundtable =
+* Supported Hardware & OS list for Firefox 4 (beltzner)
+** many questions from OSX, JS and build teams about this
+** beltzner gathering data about usage in {{bug|582848}} as well as from [http://stats.wikimedia.org/wikimedia/squids/SquidReportOperatingSystems.htm secondary sources]
+** current proposals are:
+*** drop OSX 10.4 (ease of coding, speedups from using better APIs)
+*** drop PPC (no OOPP support planned, no JM support planned)
+*** maintain W2K (no impact to coding schedule, not a lot of additional work)
+*** add OSX 64-bit (OOPP support planned, major speedup increase)
+*** do not add Windows 64-bit (no OOPP support planned)
+*** Linux 64?
+*** SSE2 is still a question
+*** beltzner to make concrete proposals to dev-planning
+*** beltzner to gather data on SSE2 usage, report to dev-planning separate from previous
+* Question for Tree Management: (zwol)
+** Try server pushes are consistently taking 13-14 hours from push to last result email.  Try server does not *appear* to be under heavier load than m-c (push rate eyeballs about the same); why is there such a huge difference?
+*** Try push load for July is ~65% higher than mozilla-central
+*** Build or test requests cannot be consolidated together on try, but can be consolidated during peak load on mozilla-central.
+*** All builds on TryServer are full-clobber builds, not incremental builds like on mozilla-central
+*** No fast build machines for try.  Shuffling from mozilla-central and other project branches would slow those down.
+*** If we ordered new hardware today, it would be at least 4 weeks to be racked up, installed, etc.  No hardware has been ordered as yet.
+*** Not all available testing slaves are currently enabled due to snow-ball effect during high jobs load. {{bug|563458}}