Platform/2009-02-17

From MozillaWiki

« previous week | index | next week »

Notices / Schedule

Firefox 3.0.7

• Builds being made

Firefox 3.0.8

• Schedule on the wiki
• Code freeze March 17
• Queries to blockers on the wiki; emails coming shortly

Firefox 3.1 Beta 3

• 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 PST
  • QA Start on ??, 9:00am PST
  • Release on ??, noon PST

Blocker Report

• 35 blocker nominations (+14 w/w)
• 147 blockers left (-10 w/w)
  • 245 left to be fixed on branch (+10 w/w)

Since 1.9.1 branch …

Past 2 weeks …

[ Platform Blocker Queries | Front End Blocker Queries ]

• stats breakdown
  • 20 blockers marked fixed1.9.1 over last week (-27 w/w)
  • 34 bugs nominated for blocking over last week (+9 w/w)
    • blocking-firefox3.1+: 4 new unresolved (+0 w/w),2 new resolved blocking-firefox3.1+ added (-2 w/w)
    • blocking1.9.1+: 16 new unresolved (-19 w/w),11 new resolved blocking-firefox3.1+ added (-8 w/w)
  • 10 patches approved for 1.9.1 over last week (-14 w/w)
  • 77 blockers are FIXED but not yet landed on 1.9.1 (+21 w/w)

Firefox 3.1 Update

• Blockers: 27 remaining (+0 w/w) & 1 nomination
  • 2 Blockers to be fixed for Beta 3 (P1)
    • beltzner: bug 475100 – name change for B3, ready to land
    • dietrich: bug 478258 – Firefox 3.1 bookmarks become unusable on PPC
  • 25 Blockers to be fixed for RC (P2) (+0 w/w)
    • aiming to be done or mostly done by Feb 23rd
  • 2 blockers need 1.9.1 landing (waiting for after string freeze)

• Polish update: Firefox is 38% shiny (+5% over last week)
  • (faaborg is OOTO this week, someone else should read this on the call)
  • Thanks go to: mstange, highmind63, and Dao
  • 49 remaining easy polish bugs (whiteboard [polish-easy])
  • 32 remaining hard polish bugs(whiteboard [polish-hard])

GFX 1.9.1 Update

• 2 blocking 1.9.1+
• 1 P1 – ebay image issue; patch bounced due to weird crash, relanding today.
• 2 P2, one with fix going in soon, one with final patch going up today, hopefully landing today
• 2 nom
  • both need to be reproduced/confirmed better than what’s there now, keeping on list until we can do that

Layout 1.9.1 Update

• No P1s
• Layout
  • 5 blockers
    • 2 need landing
    • 1 needs review
    • 2 without patches.
• SVG
  • 2 blockers
• Video/Audio
  • 15 blockers
  • Should bump most of these to ‘wanted’ to reflect reality
• 9 untriaged noms

Content 1.9.1 Update

• 25 blockers, going up!
  • Looks like there are several bugs that need landing. They look like they’ve all the needed reviews, but not sure what state they are in. Not sure if this is good or bad, but someone should go through and make sure we’re going ahead and landing and closing bugs that are actually fixed.
  • Looks like there’s a few networking bugs that will need biesi review. Is he responsive?
  • 8 Without patch.
  • 1 Has a patch, but looks to need modifying to land on trunk.
  • 13 need review.
  • 5 need landing.

• 5 untriaged nominations

• Worked with Andreas and Igor on watchdog thread issues.

JS 1.9.1

• 53 blockers
  • 11 P1s
  • 35 P2s
  • 5 P3-5s
  • 2 unprioritized
• 4 untriaged nominations
• mostly where we are last week, though we closed a few bugs last week
• need to merge, which will fix 6/12 of our remaining bugs
• 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 😉

General 1.9.1 Updates

• 4 blockers
  • 0 P1
  • 4 P2
• 2 untriaged nominations
• untriaged nominations outside of Firefox/Core/Toolkit

Security

Security Reviews

Still outstanding / to be scheduled

• native JSON
• DNS prefetching

Booked but not yet completed

Roundtable

Greener tinderbox

• clint to set up 3 machines (one for each platform) and run it for a week to log random-oranges; clint will also compare VM to native to see if there are problems caused by that
  • clint to file bugs to get machines set up
  • clint to talk to alice about her experience

Getting crash stacks from unit tests

• ted checked in breakpad clients into the tree and has build system uploading symbols to the ftp servers
• sayrer is going to make a python hook in the event of the crash

Move from VS8 -> VS9? (joduinn)

• New requirement from mobile for VS9
• Can we move mozilla-central/mozilla1.9.1/tracemonkey to use VS9 also? Code dependencies? Schedule?
  • may will need to recreate the jemalloc code patches, see bug 416117 (vlad)
  • please do not switch compilers on the active 3.0.x branch (dveditz)
  • should run performance numbers to see if things change (dbaron)
  • see if we can figure out how to make the slave pick the compiler based on the source tree