Firefox3.1/StatusMeetings/2009-01-07
< Firefox3.1 | StatusMeetings
Jump to navigation
Jump to search
« previous week | index | next week »
Firefox Product Delivery Meeting Details
- Wednesdays - Firefox 3 - 11:00am Pacific, 2:00pm Eastern, 18:00 UTC
- Mozilla Building S
- 650-903-0800 or 650-215-1282 x92 Conf# 8605 (US/INTL)
- 1-800-707-2533 (pin 369) Conf# 8605 (US)
- irc.mozilla.org #shiretoko for backchannel
NOTE: See Platform#Meeting_Notes for development meeting notes
Firefox 2.0.0.x / 3.0.x
- Firefox 2.0.0.20 -> 3.0.5 Major Update
- Going live tomorrow, January 8
- Has a new major update banner, which we're hoping encourages users to upgrade
- Aiming for converting 50% of current Firefox 2 users (right now ~16m ADUs)
- Firefox 3.0.6
- Release set for early February
- Code freeze is tonight, January 7 at 11:59pm
- Still 15 bugs that need checkin
Firefox 3.1 Development
(see development meeting notes)
Daily users
- ~300k users on the Firefox 3.1 Beta 2
- ~12k users on Shiretoko nightlies
- ~5k users on Minefield nightlies
- String freeze has been declared
- Code freeze is January 13th, 11:59pm PDT
- at yesterday's development meeting, this date was declared to be at risk due to the number of remaining P1 blockers on the Platform::JS side; currently investigating
- QA Start is January 15th, 9:00am PDT
- Release is targeted at January 26th
Support
- Weekly Issues have not changed, except one new issue:
- Facebook image uploader (Java) app causes backwards typing. bug 256763
- Plan for Firefox 3.1 Support update.
- Plan for Firefox 2 Support EOL.
- Updating the KB with 3.1 content has begun. Big thanks to Bo for doing much of the updating.
- MUs always cause support traffic to spike, so the next few days are a good time to get involved.
Localization
- Down from 29 to 18 locales at risk for B3 with outreach late last year, 2 locales at risk for release
QA
- Beta 3 testplan posted
- Added financial websites testing
- Firefox 3.1 Feature testing progress:
- Testplans (90% completed)
- Testcases (76% completed)
- QMO forums is up and running and support questions are inevitable. What's the best way to collaborate with SUMO team?
- 3.1 Litmus unclear tests/results being cleaned up right now (tracy)
Release Engineering
- FF2.0.0.20 -> FF3.0.5 MU tomorrow
- Funnelcake early next week
- win32 machines couldnt keep up with requests yesterday bug 472411
Add-Ons
- Add-Ons are now 54% compatible with Firefox 3.1 (up 20% from mid December)
Evangelism
- Web workers docs in good shape, offline stuff is next
- Shuttle demo is hacked together, has issues on windows
- Talking with twitter about some access control / XHR stuff - not sure how far it will go
- Looking for other canvas demos, etc
- Discussion: major web properties contacts
Marketing/PR
- Work started on site revisions > JSlater making first copy pass at 2 major pages:
Needs:
- Review of copy updates/changes (Beltzner, Vlad, Damon)
- Speed chart > Fx 3.1 vs. 3.X vs. Fx2 - need help to get numbers. Want to be able to make a claim of 2X or 3X faster and have a visual comparison
- Video > "what's new" > work out script for 2-minute video (Beltzner?)
- Video > embedded on FirstRun page -- scope for TRO (Doves animation)
- Demo(s) > synch with Blizzard on what's being created and where/how to include in site
Roundtable
- RRRT
- Firefox 2.0.0.20 -> 3.0.5 Major Update RRRT Page has been created and be found here - Tomcat
- Contact list for major web properties
- motivation is to get involvement of website developers earlier, especially those working on marquee web applications and websites we know are popular with Firefox users; never want to see a "Twitter breaks with Firefox 3.1" sort of thing if we can avoid it
- building a list (on Intranet, to respect privacy) here
- if you have a contact to add, please do so, or email blizzard@moz with the info if you don't have access to the page
- want to be able to have contacts to get involvement at all stages:
- development: testing, help prioritizing work, input to direction
- qa/release: testing, problem resolution
- active product: problem resolution
- Plugin security checkup
- want to make sure we don't stall on a page on mozilla.com that we can send users to in order to ensure they're up to date on plugins (not extensions, but plugins)
- work is being tracked in bug 391433 and bug 465890