Firefox2/StatusMeetings/2006-03-07: Difference between revisions

Line 13: Line 13:
== Features ==
== Features ==
* '''Places infrastructure (performance, stability, toolbar drag & drop)'''
* '''Places infrastructure (performance, stability, toolbar drag & drop)'''
** ''now on trunk, ready for branch?''
** ben is porting bugs over to branch, plan to turn it on by default tomorrow
** ''estimated time remaining for A1 readiness''
** ui is known to be annoying, but internals seem solid enough for a developer preview


* '''Undo Close Tab'''
* '''Undo Close Tab'''
Line 23: Line 23:


* '''Extension Blacklisting'''
* '''Extension Blacklisting'''
** Extension Manager code reviewed. XUL / JavaScript code to be reviewed. Should land soon dependent on it getting reviewed.
** Extension Manager code reviewed. XUL / JavaScript code to be reviewed. Should land soon dependent on it getting reviewed. (mscott in queue to do reviews)
** going to implement darin's review comments


* '''Extension Dependencies'''
* '''Extension Dependencies'''
Line 29: Line 30:


* '''Search Plugin Format Changeover (with sherlock import)'''
* '''Search Plugin Format Changeover (with sherlock import)'''
** ''patch reviewed?''
** made some Sherlock fixes
** new patch to be posted today, will need review


* '''Spell-As-You-Type (english only)'''
* '''Spell-As-You-Type (english only)'''
** we are clear to ship en-US with the product
** we are clear to ship en-US with the product
** all other dictionaries must be downloaded explicitly as XPIs, mscott maintains a [http://www.mozilla.com/thunderbird/dictionaries.html list of these extensions]; these are the same dictionaries/problems that OpenOffice has. (cbeard: we can do better! ;-) perhaps we can license or buy dictionaries and release under a compatible license? rebron is going to dive into this.  we should continue on the current path regardless.)
** all other dictionaries must be downloaded explicitly as XPIs, mscott maintains a [http://www.mozilla.com/thunderbird/dictionaries.html list of these extensions]; these are the same dictionaries/problems that OpenOffice has. (cbeard: we can do better! ;-) perhaps we can license or buy dictionaries and release under a compatible license? rebron is going to dive into this.  we should continue on the current path regardless.)
** ''enable this on branch by default? where do we package the dictionary file?''
** started porting this to branch, to be finished today or tomorrow
 
** shouldn't need that much bake time before we make A1


* '''Instrumentation Infrastructure'''
* '''Instrumentation Infrastructure'''
** ''landed on trunk?''
** code landed on trunk and on branch
** nothing for it to talk to, still blocked on server-side & storage space
** in parallel, modifications are made on the client
** hope to test server by end of the month


* '''RSS parser'''
* '''RSS parser'''
Line 44: Line 49:


* '''RSS content detection (?)'''
* '''RSS content detection (?)'''
** ''has this landed for branch?''
** landed on trunk and branch
** there is another piece of work about how to resolve conflicts between multiple sniffers, but that can land in parallel
** with API there, some UI can be created when we detect that a page is a feed. Robert Sayer is interested in doing this.


== Release Issues & Timing ==
== Release Issues & Timing ==
Line 51: Line 58:
** trunk will become browser/3.0a1, 1.8_BRANCH will become Bon Echo/2.0a1
** trunk will become browser/3.0a1, 1.8_BRANCH will become Bon Echo/2.0a1
* plan is to promote this as developer only release, low-key announce
* plan is to promote this as developer only release, low-key announce
* ''any updates from QA/Software Update questions raised last week?''
* need 3-4 days after code complete
** '''action:''' schrep to talk to preed about when we could push an alpha1
** '''action:''' need to test 1.5->2.0 update behaviour (darin to send timr testcases)
*** Axel: is this codepath or UI testing? should l10n be concerned?
*** darin: it's both, so there may indeed be localization concerns
*** rob_strong: remember that right now the check for extension compatibility check only returns extensions that have compatibility updates, not full upgrades
*** cbeard: do we want to have a mirror of AMO to have a better bring-up experience for extensions?
*** rob_strong: let me think about that, but we can probably accomplish the same effect on AMO at the moment.
*** '''action:''' rob_strong to co-ordinate with shaver on this
** '''action:''' need to get 1.8 nightly updates for the branch again


= Status Updates =
= Status Updates =
Confirmed users, Bureaucrats and Sysops emeriti
3,599

edits