Confirmed users
2,679
edits
Platform/2010-08-03: Difference between revisions
→Roundtable
(→Layout) |
|||
| (15 intermediate revisions by 10 users not shown) | |||
| Line 9: | Line 9: | ||
'''Previous release post-mortems''' | '''Previous release post-mortems''' | ||
* Firefox 3.6.7/8: 2010-08-03 @ 1:00 pm PST, duration 45 mins | * 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 | * 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 | ** The details on how the post-mortem will be run will be sent out today | ||
| Line 20: | Line 20: | ||
* missed code freeze for Firefox 4 Beta 3 due to leaks in Firefox Sync | * 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 a sustainable pattern | ** [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 = | = Blocker Report = | ||
| Line 28: | Line 32: | ||
** Code freeze is currently scheduled for Thursday August 12 @ 11:59 pm PST | ** 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 | ** 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''' | '''Firefox 3.5.12''' | ||
| Line 35: | Line 40: | ||
'''Firefox 4 Beta''' | '''Firefox 4 Beta''' | ||
* a handy list of [[Firefox/4/Triage|triage queries]] is available for all! | * a handy list of [[Firefox/4/Triage|triage queries]] is available for all! | ||
** Beta | ** 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 204 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%3Abeta,final 222 blockers] (462 total) | ** Final: [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=blocking2.0%3Abeta,final 222 blockers] (462 total) | ||
| Line 47: | Line 52: | ||
== GFX == | == GFX == | ||
* Going to make enabling Direct2D a Beta | * 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. | * 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 == | ||
* JS fatvals landed | * JS [http://blog.mozilla.com/rob-sayre/2010/08/02/mozillas-new-javascript-value-representation/ fatvals] landed | ||
* ES5 | * ES5 | ||
** Landings | ** Landings | ||
| Line 72: | Line 75: | ||
* Content/chrome rendering integration | * Content/chrome rendering integration | ||
** Timothy needs help | ** Timothy needs help | ||
* -moz-font-feature-settings has landed ("Land CSS control of lowlevel font features" done) | |||
** Needs Harfbuzz enabled to work | |||
== Video == | == Video == | ||
* Improved software scaling ready to land | * Improved software scaling ready to land | ||
* Standards compliance fixes | |||
** 'autobuffer' -> 'preload' | |||
** New load algorithm | |||
= Windows 7 Test Status = | = Windows 7 Test Status = | ||
| Line 95: | Line 103: | ||
*** add OSX 64-bit (OOPP support planned, major speedup increase) | *** add OSX 64-bit (OOPP support planned, major speedup increase) | ||
*** do not add Windows 64-bit (no OOPP support planned) | *** 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) | * 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 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}} | |||