Firefox2/StatusMeetings/2006-02-28: Difference between revisions

m
omg, I just alphebetized that ... nerrrrd!
m (omg, I just alphebetized that ... nerrrrd!)
 
(17 intermediate revisions by 7 users not shown)
Line 2: Line 2:


= In Attendance =
= In Attendance =
annie, axel, autonome, beltzner, ben, bsmedberg, brakowski, brettw, darin, dveditz, gavin, jhughes, mconnor, markp, rebron, rob_strong, timr


= Agenda =
= Agenda =
Line 11: Line 12:
== Features ==
== Features ==
* '''Places infrastructure (performance, stability, toolbar drag & drop)'''
* '''Places infrastructure (performance, stability, toolbar drag & drop)'''
** performance (Tp, Ts) has gotten better, close to status quo if not better
** problems with memory leak on balsa that we're trying to track down; this is blocking us as we can't turn it on. We're not sure that this is even Places that's doing it.
*** dveditz: the whole point of "WARN_IF_FALSE" was to warn instead of fail on an assertion.
*** darin: I'm gonna rack that up to maybe a typo in nsDebug.h?
*** ben: maybe we can flip places on?
*** beltzner: will post to devnews tonight, then flip it on for Weds morning
* '''Undo Close Tab'''
* '''Undo Close Tab'''
** at a hard decision about what approach to take
*** either hide-the-tab, try to leverage bfcache, or just try to preserve form data retention
** will be able to get it ready for A1 based on one of these directions, assuming we still want to
*** beltzner: I think we should get at least one of these directions in place
** darin: why would we use bfcache?
** bsmedberg: it might help persist full state while not allowing plugins and media to run in the background (which would happen with hide-the-tab)
** darin: need to be careful about <code>onunload</code> handlers and other things that disable bfcache
** mconnor: if I can't figure out a way to make it work consistently, we might want to push this off to A2 or even extension-land
* '''Tab Overflow'''
* '''Tab Overflow'''
**
* '''Extension Blacklisting'''
* '''Extension Blacklisting'''
** patch waiting for review
* '''Extension Dependencies'''
* '''Extension Dependencies'''
** landed, no regressions
* '''Search Plugin Format Changeover (with sherlock import)'''
* '''Search Plugin Format Changeover (with sherlock import)'''
** review going well, working through Ben's comments
** not going to move to toolkit based on feedback in d-a-f
** looking to have a new patch for review soon (today/tomorrow)
* '''Spell-As-You-Type (english only)'''
* '''Spell-As-You-Type (english only)'''
** it's on trunk already (without the dictionary) --enable-extension: spellcheck? there are instructions in the enable spell check bug
** still blocked on licensing, who do I talk to about this? mscott for starters.
** ben: where does the dictionary file? what needs to happen with the build system to get it included?
** bsmedberg: point me to that please and we can get this started
* '''Instrumentation Infrastructure'''
* '''Instrumentation Infrastructure'''
** good progress on getting server infrastructure up and running
** should move this off to A2
** the exit survey will be in place for Firefox 1.5.0.2, morgamic is doing the final bits of work for the web app
*** also thinking about entrance survey
*** action '''beltzner''' cc darin on bug 314119
* '''RSS parser'''
* '''RSS parser'''
** ben needs to check in with robert, think it's stuck waiting for a review
* '''RSS content detection (?)'''
* '''RSS content detection (?)'''
** we ''think'' we're good here; not in darin's review queue anymore, at any rate


== Blockers ==
== Blockers ==
* version number / branding
* version number / branding
** currently set at 1.5, should it be 2.0a1?
** currently set at 1.5, should it be 2.0a1?
* ''any others?''
** benjamin: yes, that's what mscott's doing
 
** dveditz: should we also change the trunk, which is currently 1.6a1?
== Release ==
** benjamin: mscott has all of these under proposal
* ''should we start the countdown?''
** '''action''' beltzner to take this as an action
* davel: when we push 2.0a1 to the beta-update channel, will these users get a choice?
** darin: yes, if we set something as a "major" release, they'll get a choice
** bsmedberg: it would be a good idea to test this code path on the nightly?
** annie: I think there's a lot of users who don't realize that they're on a beta channel right now, so we shouldn't be pushing the alpha onto the 1.5 beta channel
** '''action''' for darin to synch up with preed(?) to make sure that everyone's up to speed
** '''action''' for QA to test the 1.5.x update logic for user choice
* ben: release notes? documentation for MDC?
** promote it as a developer release
** mconnor: do we even want to promote it as that? some of these APIs are going to change?
** beltzner: but we want that feedback, don't we?
** mconnor: I'm worried about getting dugg, and getting bug feedback that we don't really care about anyway
** ben: maybe do it invite only?
** mconnor: get the release download numbers from Asa


= Status Updates =
= Status Updates =
== Places ==
== Places ==
 
* performance was good, no known data corruption issues
''update from ben''
* annie's prepared some solid estimates, I need to do that and get it from the rest of the team
 
* '''action''' ben to meet with schrep next monday
Brett: "Performance is good, no known data corruption issues."


== Tabbed Browsing ==
== Tabbed Browsing ==
''update from mconnor''
* nothing beyond what's been discussed


== Extension Manager Enhancements ==
== Extension Manager Enhancements ==
''update from rob_strong''
* Extension Dependencies - phase 1 landed - no regressions so far
* Extension Blacklisting - patch ready for review last Friday
* Extension Locales - started
* Extension UI - mockups and proof of concept started


== Installer ==
== Installer ==
''update from rob_strong''
* Windows Installer - nothing new other than work on this will start again this week
** bsmedberg: is DOM Inspector part of the product or not?
** first requirement is to be able to provide variable paths for distribution and packaging of our installer
** now we're starting to talk about creating various levels of stub install: stub with full code, stub with all code but not optional code, stub with no code.
*** bsmedberg: but do we consider DOM inspector part of the application or not?
*** rob_strong: put it on AMO?
*** beltzner: we need to figure out a way to make sure that it's there for users who need it, but not there for users who aren't there
* Branding and Locale installer customization - nothing new


== Search Engine UI ==
== Search Engine UI ==
''update from gavin''
*Back end work complete
*Updated patch today or tomorrow - needs review from mconnor
**Addressed ben's SR comments
*Code to remain in /browser per discussion on dev.apps.firefox
*Re-factoring of the Sherlock parsing code to be completed seperately if time permits (low priority)
*Need to discuss search plugin format further


== Visual/UI Refresh ==
== Visual/UI Refresh ==
Line 67: Line 135:


== Instrumentation / Exit Surveys ==
== Instrumentation / Exit Surveys ==
''update from bryner''
* Mostly working on server backend.  Not much new status to report.
* {{bug|189570}} is fixed on the trunk.


== Session Saver ==
== Session Saver ==
''update from autonome''
* SessionStore service mostly working in Bon Echo
* Currently pulling from cache or reloading, not dump/restoring DOM
* This week: define and document API, finish code review and post patch


== Branding & Update Systems ==
== Branding & Update Systems ==
Line 76: Line 147:


== RSS ==
== RSS ==
''update from ben''
* need to check in with robert sayre


== Offline mode / better use of cache ==
== Offline mode / better use of cache ==
''update from darin''
* patch is in, waiting for branch approval
* continuing to investigate low hanging fruit


== Anti-Phishing ==
== Anti-Phishing ==
Line 92: Line 164:


= Other Business =
= Other Business =
* annie: maybe use Google's QA to help us here
** '''action''' annie and timr to talk about this
Confirmed users, Bureaucrats and Sysops emeriti
3,599

edits