- AMO 5.2 launched last Tuesday with support for Personas and new statistics for developers
- Kicking off Firefox 3.6 compatibility efforts. Currently at 36%
- Add-on Compatibility Reporter was announced last week
- Add-ons Meetup at 7pm tomorrow night in Mountain View, RSVP!
- Firefox 3.0.16 / Firefox 3.5.5
- proposed schedules available on the wiki
- mid-December release date… yeah.
- changing our beta period structure to push the release to beta channel earlier
- Namoroka (Firefox 3.6)
- Firefox 3.6 Beta 1 scheduled to be released Wednesday, October 28
- nightly and beta users are encouraged to help us by reporting add-on compatibility
- Paul and others will be landing a change which should speed up session restore for users with many windows and tabs
- we’d like as many people as possible to test recent nightlies and the upcoming beta with Windows 7; there’s some concern about how well the implementation of Aero Peek tab previews are working (see bug 474056 and dependencies)
- there’s an ongoing discussion about how we plan on updating Firefox 3.5 users to Firefox 3.6 when it’s ready for release
- Firefox 3.7
- Stephen Horlander continues to QB discussions about changes to the Firefox 3.7 theme on the wiki and his blog
- Alex Faaborg and the UX team are looking at how to simplify our Preferences panels
- Jennifer Boriss, Dave Townsend and Nick Nguyen are looking at updating the Add-on manager and Extensions API to be more flexible
- we’re also starting to think about how to phase in process separation in Firefox 3.7 and 4.0
- Gecko 1.9.2
- In our CrashKill meetings we are still digging through top crashers and reaching out to vendors. We still need contacts for vendors who produce top crashing add-ons. If you have contacts at one of these that you can share, please comment in the bug. Also, if you want to keep the contact info confidential, you can mark your comment as private as well.
- Thanks to BitDefender who is pushing out fixes to their toolbar in response to our outreach. It’s still early, but we’re watching crash reports to make sure we see those crash numbers drop.
- Team blocker numbers:
- SpiderMonkey Happenings
- Continuous Perf Improvements
- ES5 coming together well
- Most blockers seem to be well understood
- TBird 3.0RC1 (Shredder)
- No Report