Platform/2009-05-05: Difference between revisions
< Platform
Jump to navigation
Jump to search
| Line 40: | Line 40: | ||
=== Browser / Front End === | === Browser / Front End === | ||
* Blockers: [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&product=Firefox&product=Toolkit&keywords_type=nowords&keywords=fixed1.9.1+verified1.9.1&resolution=---&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=blocking1.9.1%2B&field0-0-1=flagtypes.name&type0-0-1=equals&value0-0-1=blocking-firefox3.5%2B&field0-1-0=resolution&type0-1-0=noop&value0-1-0=INVALID+WONTFIX+WORKSFORME+INCOMPLETE+MOVED+EXPIRED | * Blockers: [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&product=Firefox&product=Toolkit&keywords_type=nowords&keywords=fixed1.9.1+verified1.9.1&resolution=---&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=blocking1.9.1%2B&field0-0-1=flagtypes.name&type0-0-1=equals&value0-0-1=blocking-firefox3.5%2B&field0-1-0=resolution&type0-1-0=noop&value0-1-0=INVALID+WONTFIX+WORKSFORME+INCOMPLETE+MOVED+EXPIRED 11 remaining] & [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&product=Firefox&product=Toolkit&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=blocking1.9.1%3F&field0-0-1=flagtypes.name&type0-0-1=equals&value0-0-1=blocking-firefox3.5%3F 5 nominations] | ||
** | ** two tricky things (undo close window fallout, tab drag and drop) | ||
** big props to Johnath and Dietrich for getting {{bug|486236}} handled | ** big props to Johnath and Dietrich for getting {{bug|486236}} handled (again!) | ||
* Polish update: Firefox is 55% shiny (+2% over two weeks ago) | * Polish update: Firefox is 55% shiny (+2% over two weeks ago) | ||
Revision as of 18:05, 5 May 2009
« previous week | index | next week »
Notices / Schedule
- Firefox 3.0.11
- code freeze tomorrow at 11:59pm
- only a few blockers left though
- released last week
- contains lots of great stuff
- well received so far!
- beltzner to discuss schedule, fill in notes
Blocker Report
Since 1.9.1 branch ...
Past 2 weeks ...
[ Platform Blocker Queries | Front End Blocker Queries ]
Summary
- slow week due to all hands
- need to keep pressure and pace up!
The Breakdown
- 6 blockers marked fixed1.9.1 over last week
- 21 bugs nominated for blocking over last week
- blocking-firefox3.5+: 7 new unresolved, 2 new resolved blocking-firefox3.5+ added
- blocking1.9.1+: 12 new unresolved, 7 new resolved blocking1.9.1+ added
- 14 patches approved for 1.9.1 over last week
- 77 blockers are FIXED but not yet landed on 1.9.1
- 38 bugs with approval1.9.1+ that are not yet landed on 1.9.1
Browser / Front End
- Blockers: 11 remaining & 5 nominations
- two tricky things (undo close window fallout, tab drag and drop)
- big props to Johnath and Dietrich for getting bug 486236 handled (again!)
- Polish update: Firefox is 55% shiny (+2% over two weeks ago)
- Thanks go to: marco, dao
- 44 remaining easy polish bugs (whiteboard [polish-easy])
- 38 remaining hard polish bugs(whiteboard [polish-hard])
GFX 1.9.1 Update
- 5 blocking bugs
- 4 of them are image rendering related, either perf or artifacts when zooming
- 1 is the nsWindow destroy bug, which our bandaid attempt didn't fix
Layout Update
- Roc is not available today
- Layout
- 5 blockers on trunk (3 with patches)
- 10 untriaged noms (3 fixed)
- SVG
- 0 blockers
- Video/Audio
- 19 blockers (6 with patches) (could be pruned, should not delay our schedule)
Content Update
Mac OS X Update
JS 1.9.1
23 blockers, around 4 with patches in hand. 5 noms.
General 1.9.1
Mobile 1.9.1 Update
Security
Multi-Process
- Initial docs with phases and SWAG schedule available.
- Initial focus will be responsiveness/stability, not security sandboxing
- We're looking for places where chrome JS currently touches content DOM directly... see mozilla.dev.platform post for more details.
- Decisions need to be made about how to approach the network stack (should we switch to chromium's network stack wholesale?), but I don't know the right way to have that conversation/make that decision (it's hard to know whether switching would reduce or extend the total time of the multiple-process work).
Tree Management
Roundtable
- If you worked on a user facing feature, please make sure it is on this list (which will be used to generate the press reviewer's guide, mozilla.com content, etc):