Confirmed users
2,679
edits
Firefox3.1/StatusMeetings/2009-02-04: Difference between revisions
Firefox3.1/StatusMeetings/2009-02-04 (view source)
Revision as of 19:16, 4 February 2009
, 4 February 2009→Release Engineering
m (→QA) |
|||
| (14 intermediate revisions by 9 users not shown) | |||
| Line 14: | Line 14: | ||
== Firefox 2.0.0.x / 3.0.x == | == Firefox 2.0.0.x / 3.0.x == | ||
* [[Releases/Firefox_3.0.6|Firefox 3.0.6]] | * [[Releases/Firefox_3.0.6|Firefox 3.0.6]] | ||
** [[Releases/Firefox_3.0.6/RRRT | Firefox 3.0.6]] | ** Shipped yesterday evening | ||
** [[Releases/Firefox_3.0.6/RRRT | Firefox 3.0.6 RRRT page]] | |||
** RRRT report: The RRRT Team (thanks Rey!) got a report about Problems/Timeouts during the Updates to Firefox 3.0.6. After investigation also other people have seen this Problem. RRRT has informed Release - Drivers and Sam has throttled Updates {{Bug|476875}} - Tomcat | |||
** Tracking any other issues and ensuring this one is fixed | |||
* [[Releases/Firefox_3.0.7|Firefox 3.0.7]] | * [[Releases/Firefox_3.0.7|Firefox 3.0.7]] | ||
** Mostly code froze last night | |||
* | ** Might take two or three more bugs | ||
** In QA testing now | |||
** Aiming for release in early March | |||
== Firefox 3.1 Development == | == Firefox 3.1 Development == | ||
'''Development Update''' | '''Development Update''' | ||
* full [[Platform/2009- | * full [[Platform/2009-02-03|platform meeting notes]] available from yesterday | ||
* down to <10 outstanding [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=blocking-firefox3.1%3F&field0-0-1=flagtypes.name&type0-0-1=equals&value0-0-1=blocking1.9.1%3F blocker nominations], will keep this list triaged daily | |||
* down to [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&resolution=---&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=blocking-firefox3.1%2B&field0-0-1=flagtypes.name&type0-0-1=equals&value0-0-1=blocking1.9.1%2B 155 blockers without fixes] for final ship, with an average find-fix rate of 20 blockers/week | |||
* will be revving a bunch of UUIDs which may affect 3rd party plugins that have compiled binary components (virus scanners, CoolIris, that sort of thing) | |||
'''Daily users''' | '''Daily users (weekly average across versions)''' | ||
* 3.1b2 - 350k daily users | |||
* Shiretoko - 10k daily users | |||
* Minefield - 6k daily users | |||
'''[[Releases/Firefox_3.1b3|Beta 3]]''' | '''[[Releases/Firefox_3.1b3|Beta 3]]''' | ||
** [[Releases/Firefox_3.1b3/RRRT | Firefox 3.1 Beta3]] | * JS team making strong progress, one of the bigger issues looks to be resolved today (upon which many of the other issues are dependent) | ||
* no further estimate at this time | |||
* [[Releases/Firefox_3.1b3/RRRT | Firefox 3.1 Beta3 RRRT page]] is ready to go | |||
== Support == | |||
* Last week's Yahoo toolbar/login issue may be a false alarm (may just be Yahoo cookies and coincidence that they all had the toolbar). Sorry guys. | |||
* No new Firefox issues last week. | |||
* The issue with update is causing people to get error messages, will keep RRRT appraised. Quick search gave 5 new threads (some with multiple people) in the past 24 hours. | |||
== Localization == | == Localization == | ||
* Waiting for ... guess what | |||
* Fennec l10n waiting for tinderbox problems on arm-linux, {{bug|475961}} | |||
== QA == | == QA == | ||
| Line 49: | Line 66: | ||
== Release Engineering == | == Release Engineering == | ||
* no news - waiting for "go". | |||
== Add-Ons == | == Add-Ons == | ||
Current status: 76.5% compatible with 3.1 which jumps to nearly 81% once Firebug is compatible. | * Current status: 76.5% compatible with 3.1 which jumps to nearly 81% once Firebug is compatible. | ||
Emails going out today or tomorrow; delayed by Bugzilla issues which IT had to deal with. | * Emails going out today or tomorrow; delayed by Bugzilla issues which IT had to deal with. | ||
Current compatibility dashboard still counts 2.0 only extensions. Revised dashboard will ship 2/19. | * Current compatibility dashboard still counts 2.0 only extensions. Revised dashboard will ship 2/19. | ||
* Rey is going to start contacting developers that use binary components regarding the Gecko 1.9.1 update. | |||
== Partners == | == Partners == | ||
| Line 60: | Line 79: | ||
* Got Rey to post / discuss an IID change - might impact add-ons compat late in the game. Ask beltzner, he's on the mail thread. | * Got Rey to post / discuss an IID change - might impact add-ons compat late in the game. Ask beltzner, he's on the mail thread. | ||
* The [[mdc:Firefox 3.1 for developers|Firefox 3.1 for developers]] page will be getting a substantial reorganization and cleanup this week. | |||
== Marketing/PR == | == Marketing/PR == | ||
* Hand-off of designs to SilverOrange has started, should be completed by the end of the week. Goal is still to start l10n and QA by 2/15. | |||
* Refresh of Fx3 video ongoing with TRO | |||
* Outreach for more beta testers started | |||
* Updating 3.1 PR plan | |||
Needs: | |||
* Review initial draft/sections of reviewer's guide | |||
* Confirm Feb 27th to record what's new video | |||
* Timeline for Beta 3 so we can begin press outreach | |||
== Roundtable == | == Roundtable == | ||
* ''justin agreed to follow up with morgamic to ensure that we could throttle Major Update snippets on a per version / channel basis (to allow users to "Check for Updates..." to Firefox 3.1 on launch day, but not have the offer given to users who do not explicitly check)'' | * ''justin agreed to follow up with morgamic to ensure that we could throttle Major Update snippets on a per version / channel basis (to allow users to "Check for Updates..." to Firefox 3.1 on launch day, but not have the offer given to users who do not explicitly check)'' | ||