Platform/2009-03-17: Difference between revisions
< Platform
Jump to navigation
Jump to search
| Line 132: | Line 132: | ||
** Did we have the security review? Land on Trunk? | ** Did we have the security review? Land on Trunk? | ||
** see [http://groups.google.com/group/mozilla.dev.planning/browse_thread/thread/4e63eb60878b81ba dev.planning thread] on the topic | ** see [http://groups.google.com/group/mozilla.dev.planning/browse_thread/thread/4e63eb60878b81ba dev.planning thread] on the topic | ||
* Nick Nethercote will be doing a Valgrind brown bag presentation next week. All devs are encouraged to join. Nick is a core contributor to Valgrind. I'll send out a note to dev-planning with instructions on how the public can join. | |||
Revision as of 18:13, 17 March 2009
« previous week | index | next week »
Notices / Schedule
- Code freeze is today at 11:59pm
- Many people not working on their blockers; we've had to push quite a few
- How can we communicate better on code freeze dates?
- On track to ship on March 18
- Fixes on par with Firefox 3.0.7
- released, showing 320k users (120k left on 3.1b2)
- string freeze: Thursday, March 19th at 23:59 PDT
- code freeze: Monday, April 6th
- QA start: Wednesday, April 8th
- release: week of April 13th
- Shiretoko (mozilla-1.9.1 branch) nightlies have been renumbered to 3.5b4pre
- Minefield (mozilla-central trunk) nightlies have been renumbered to 3.6a1pre
- next steps are renaming AMO maxVers, changing blocking flags on Bugzilla, updating saved queries and charts, graph server links, etc
Blocker Report
- 21 blocker nominations (-37 w/w)
- 100 blockers left (+6 w/w)
- 205 left to be fixed on branch (+37 w/w!)
Since 1.9.1 branch ...
Past 2 weeks ...
[ Platform Blocker Queries | Front End Blocker Queries ]
Summary
- for the past two weeks, our find-fix rate has been close to 0
- not wholly unexpected as we've released another beta
- need to monitor this closely, and think of what this means for our b4 schedule
The Breakdown
- 17 blockers marked fixed1.9.1 over last week (-16 w/w)
- 20 bugs nominated for blocking over last week (-18 w/w)
- blocking-firefox3.1+: 2 new unresolved (-4 w/w),3 new resolved blocking-firefox3.1+ added (+2 w/w)
- blocking1.9.1+: 35 new unresolved (+21 w/w),34 new resolved blocking1.9.1+ added (+22 w/w)
- 28 patches approved for 1.9.1 over last week (-3 w/w)
- 77 blockers are FIXED but not yet landed on 1.9.1 (+29 w/w)
Browser / Front End
- Blockers: 11 remaining (+0 w/w) & 2 nominations
- Polish update: Firefox is 47% shiny (+3% over last week)
- Thanks go to: rstrong, mstange, wladow and Dao (5)
- 45 remaining easy polish bugs (whiteboard [polish-easy])
- 36 remaining hard polish bugs(whiteboard [polish-hard])
GFX 1.9.1 Update
- Bug status:
- 3 blocking 1.9.1+
- 1 security-ish bug
- 1 imglib bug waiting on review
- 1 imglib mystery crasher bug
- Focus:
- Finishing remaining blockers
- Will send mail about planning update for future work
Layout 1.9.1 Update
- Layout
- 7 blockers
- Current work: frame constructor refactoring (bz), frame GC evaluation (zwol), float bug, SXSW (dbaron), plugin widget hoisting (roc), textbox baseline alignment (karlt)
- SVG
- 2 blockers
- Current work: SVG spec work (jwatt)
- Video/Audio
- 12 blockers
- Major items remaining: A/V sync (doublec), block cache (awaiting review) (roc), seek performance (doublec), bug fixes (cpearce), playback performance (mgregan), code audit issues (more progress)
Content Update
- 1.9.1:
- 13 blockers
- 3 blockers ready to land.
- 2 blockers blocked on reviews from biesi, email sent.
- 4 untriaged nominations
- 13 blockers
- 1.9.next:
- peterv's continuing to work on slimwrappers bug slimwrapper.
- bent's making good progress on having us stay on trace while calling quickstubs.
JS 1.9.1
- 36 blockers
- 2 P1s
- 28 P2s
- 4 P3-5s
- 3 unprioritized
- 5 untriaged nominations
- bug 452498 - upvar, remains tricky, being worked
Mobile 1.9.1 Update
- Now have WinCE builds mobile tinderbox is here, YouTube Video review of it on an HTC touch is here ;)
- bug 481566 We're seeing big responsiveness wins from this patch to the content sink. Patch isn't quite what we want, but need to find what we need.
- bug 67752 Interruptible reflow -- we're also seeing big wins here, would like to trunk as soon as possible and would like to get it landed on 1.9.1 at some point if possible
- We're seeing performance wins from turning on the chrome JIT. Having trouble coming up with good tools to measure as our current ones use JSD which disables the JIT.
- Seeing a small backlog of 1.9.1 approval requests piling up, none super urgent, but need to continue to get in.
Security
Security Reviews
Still outstanding / to be scheduled
- native JSON
- DNS prefetching
Booked but not yet completed
Tree Management
- Getting crash stacks for tests
- Needs to happen on try server still bug 483111
- Run unit tests on packaged builds bug 421611, bug 383136
- Got hung up on some xpcshell test issues bug 483202, should have updated patch today with good enough workaround, basically done modulo reviews at that point
Roundtable
- Turn off the SQL logging by default (file bugs on performance problems)
- These warnings won't solve the problem, since you can't know whether you've fixed a performance problem if you don't measure it. Real bug: need performance tests for storage users, and storage itself.
- Consider localStorage feature land on 1.9.1, bug 422526
- Did we have the security review? Land on Trunk?
- see dev.planning thread on the topic
- Nick Nethercote will be doing a Valgrind brown bag presentation next week. All devs are encouraged to join. Nick is a core contributor to Valgrind. I'll send out a note to dev-planning with instructions on how the public can join.