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

From MozillaWiki
Jump to navigation Jump to search
No edit summary
 
No edit summary
Line 38: Line 38:
* axel: what's the impact for l10n repackaging?
* axel: what's the impact for l10n repackaging?
** when it lands, it will be no different than our current solution for repackaging
** when it lands, it will be no different than our current solution for repackaging
* bsmedberg: we can still land this in an installer2 directory for now
* should be ready for A2
* need to create a single tracking bug
* axel: what's the license
** mpilgrim: seems to be ZLIB


== ==
== Search Engine UI ==
* gavin sharp is pursuing this, will be granted ownership
* ben has asked him to triage the bugs and set target milestones
* starting from the prototype from last year
* not ready for current A1 target date
* axel: are we changing the format for the searchplugins for 2.0?
** ben: yes, to an XML format that is similar but not necessarily identical to OpenSearch
** mconnor: and we'll provide a converter
 
 
==  


- autoupdate bugs
- autoupdate bugs
- polish bugs
- polish bugs

Revision as of 19:30, 7 February 2006

In Attendance

phone: mpilgrim, axel, bsmedberg room: schrep, cbeard, timr, rebron, rob_strong, jesse, dietrich, timr, davel, beng, darin, bryner, annie, brettw, linus, maria, beltzner, mconnor, pgreen

Status Updates

Places

  • organized bugs into four categories:
    • a1/dogfood
    • a2/feature complete
    • b1/feature frozen
    • b2/future
    • these are target milestones
  • still working through performance problems and not-working things
  • not sure if things will be ready for current A1 target
    • want to ensure that there's no dataloss or instability problems before a1
    • hoping to be ready no later than 2 weeks from now
    • might want to cut alpha1 without --enable-places
  • davel: be sure to include pointers to test plans and tools and hooks
  • changes are being checked into trunk and 1_8_BRANCH at the same time

Tabbed Browsing

  • close-buttons-on-tabs currently on trunk (ready for A1)
  • undoCloseTab hacked up solution in place, need to figure out UI
  • still working on tab overflow solutions, focusing on making it feel right
    • solution in progress seems to be to use [<<] / [>>] buttons at each end
  • won't be ready for current A1 target

Extension Manager Enhancements

  • working on blacklisting, extension dependencies and support for locale packs, all of which are intertwined
    • on track to hit A1 target
  • some of the UI designs required a browser-notification system which isn't going to hit, so we'll need to revisit the UI
  • plans in place to change the extension manager UI, but haven't started work on that yet

Installer

  • w32 only, moving to nSysInstaller (nullSoft/OSS), saves us 130K on the installer size, gets rid of our previous solution which was pretty messy
  • pretty much ready to go, just need to merge to tree
  • mpilgim: there's an existing bug on file for supporting installers in high contrast themes, be sure to test your new solution on that, too.
  • axel: what's the impact for l10n repackaging?
    • when it lands, it will be no different than our current solution for repackaging
  • bsmedberg: we can still land this in an installer2 directory for now
  • should be ready for A2
  • need to create a single tracking bug
  • axel: what's the license
    • mpilgrim: seems to be ZLIB

Search Engine UI

  • gavin sharp is pursuing this, will be granted ownership
  • ben has asked him to triage the bugs and set target milestones
  • starting from the prototype from last year
  • not ready for current A1 target date
  • axel: are we changing the format for the searchplugins for 2.0?
    • ben: yes, to an XML format that is similar but not necessarily identical to OpenSearch
    • mconnor: and we'll provide a converter


==

- autoupdate bugs - polish bugs