Platform/2009-02-03
From MozillaWiki
< Platform
« previous week | index | next week »
Contents
Notices / Schedule
- Code freeze today at 11:59pm
- Please land your approval1.9.0.7+ patches when the tree turns green again :(
- Blockers needing 1.9.0.7 patches (down to only a handful)
- More queries available on the wiki
- (Also shipping Firefox 3.0.6 today)
- we will go over the list of P1 blockers outstanding in this meeting and ensure they are being tracked
- Important Dates:
- Code freeze was missed on January 25th, 11:59pm PDT
- QA Start on ??, 9:00am PDT
- Release on ??, noon PDT
- Markus Stange made an incredibly useful tool
Blocker Report
Since 1.9.1 branch ...
Past 2 weeks ...
[ Platform Blocker Queries | Front End Blocker Queries ]
- stats breakdown
- 100 blockers marked fixed1.9.1 over last week
- 39 bugs nominated for blocking over last week
- blocking-firefox3.1+: 12 new unresolved,8 new resolved blocking-firefox3.1+ added
- blocking1.9.1+: 44 new unresolved,90 new resolved blocking-firefox3.1+ added
- 23 patches approved for 1.9.1 over last week
- 54 blockers are FIXED but not yet landed on 1.9.1
Firefox 3.1 Update
- Blockers: 33 remaining (+2) & 2 nominations
- 2 Blockers to be fixed for Beta 3 (P1)
- beltzner: bug 475100 - name change for B3
- sdwilsh: bug 476292 - patch in hand - writing test. ETA EOD today
- 31 Blockers to be fixed for RC (P2)
- time estimates being generated this week
- 2 blockers need 1.9.1 landing (waiting for after string freeze)
- see also these other triage queries
- 2 Blockers to be fixed for Beta 3 (P1)
- Polish update: Firefox is 31% shiny (similar change of +2% over last week)
- Thanks go to: Shawn, Dao, Ehsan, and Drew
- 49 remaining easy polish bugs (whiteboard [polish-easy])
- 36 remaining hard polish bugs(whiteboard [polish-hard])
GFX 1.9.1 Update
- 4 blocking 1.9.1+
- 1 P1 with patch, needs-landing
- 2 P2 with patch, needs-landing
- 1 P2 got backed out yesterday (on 1.9.1 only, trunk was red so didn't back out there yet; will back out on trunk today)
- 1 untriaged nominations (that I've looked at, will decide blocking/etc. based on difficulty)
Layout 1.9.1 Update
- 7 blockers
- 8 untriaged nominations
- SVG
- 3 blockers
- Video/Audio
- 14 blockers
Content 1.9.1 Update
- 17 blockers
- P1
- none, yay!
- 14 P2s
- 1 P3
- 2 unprioritized
- P1
- 1 untriaged nominations
JS 1.9.1
- 50 blockers
- 14 P1s
- 26 P2s
- 5 P3-5s
- 5 unprioritized
- 14 untriaged nominations
- actually flat for bugs this week (stuff's FIXED in tracemonkey tree, but not yet merged and marked fixed on m-c or 191)
- things are getting better
- bunch of P1s that depend on a single P1 is hours away from landing
Mobile 1.9.1 Update
- Now have WinCE builds mobile tinderbox is here, YouTube Video review of it on an HTC touch is here ;)
General 1.9.1 Updates
Security
Security Reviews
Still outstanding / to be scheduled
- native JSON
- DNS prefetching
Booked but not yet completed
Roundtable
Dealing with the iid rev stuff that came up in .platform before b3?
- bunch of interfaces changed from 1.8 -> 1.9 that didn't rev the UUID
- bsmedberg and bz want to add these as P1 blockers for 1.9.1b3
- con: adds blockers, people may have already been compiling against b2, pro: right thing to do
- decided to do it
- beltzner will contact AMO and Evangelism folks
- details at http://groups.google.com/group/mozilla.dev.platform/browse_thread/thread/3bd5f5599caf2e14
Tony asked if there's anything QA can do to extend testing?
- beltzner: banks, webmail, ebay and online apps
- shaver: sites that have historically caused problems with betas, test coverage across operating systems
Interruptible reflow
- bz says that it's sorta working, lots of assertions firing, layout regressions on reftests being debugged. Not going to be ready this week; we'll see about next week.