Firefox3.1/StatusMeetings/2008-06-24

« previous week | index | next week ... Firefox 3.1! »

Firefox 3.1/Gecko 1.9.1 Meeting Details

• Tuesdays - Firefox 3 - 11:00am Pacific, 2:00pm Eastern, 18:00 UTC
• Mozilla Building S
• 650-903-0800 or 650-215-1282 x91 Conf# 217 (US/INTL)
• 1-800-707-2533 (pin 369) Conf# 217 (US)
• irc.mozilla.org #shiretoko for backchannel

Firefox 3.1

• purpose of this meeting (fill in notes later)

• going over scope (fill in notes later)
  • product side
  • platform side
  • things that don't get into 3.1 slide into 4

• Places (dietrich, marco?, mano?, sdwilsh?)
  • query builder: bug 436380, being de-prioritized
  • awesomebar enhancements: show keywords bug 392143?, edit middle bug 407888?, restrict match bug 395161?
  • performance issues: allowing people to delete things, fsync, query performance in transaction manager, mozStorage/SQLLite
  • tagging UI: autocomplete ((bug 415960)), quick tagging UI (bug 434946), bulk tagging/editing (bug 412002)

• Misc Projects
  • clare: working on EM to get better indication of compatibility for updates
  • paul: cleaning up UI/behaviour at shutdown, working on pwd manager stuff with justin
  • justin: looking at feasibility of more site-specific notifications/UI from the site identity button, form manager triage, notification work, performance work

• Install/Update
  • Software update priv elevation, OS integration on Vista

backend

• performance work on JS
• <video> tag
• ACID 3 improvements
• keith: CSS transform property
• SMILE (animated SVG)
• SVG-CSS properties
• vlad working on pixman/cairo perf
• offline fixes
• worker threads

Triage Etiquette

• new features are very unlikely to be blockers
• regressions & must haves are blockers
• want-to-haves are "wanted"
  • wanted-P1s: a good set of these items makes a compelling release
  • wanted-P2s: medium running task, not as high priority
  • wanted-P3s: nice to have, would take patches / apply some effort here

Proposed Schedule (draft, not final)

• ship in 4Q/08 or 1Q/09
• first alpha in july
  • when can we be API frozen?
  • when can we expect to be feature frozen?
• first beta in august
  • when can we expect features to land?
• KaiRo: feature freeze for platform is an important date for other apps building on the toolkit (both SM2 and TB3 look to be targetting 1.9.1)

Localization

• not at all set up on Mercurial
• need support from IT and Build to get this ready
• need to get this ready for the first beta

QA

• none this week

Build

• build automation needs to be tested/confirmed as working with Mercurial
• down a man for the next few weeks

Round table

• upcoming bugzilla reorg.