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

m
no edit summary
mNo edit summary
 
(18 intermediate revisions by 8 users not shown)
Line 1: Line 1:
<small>[[Firefox2/StatusMeetings/2006-02-14|<< previous week]] | [[Firefox2/StatusMeetings|index]]</small>
<small>[[Firefox2/StatusMeetings/2006-02-14|<< previous week]] | [[Firefox2/StatusMeetings|index]] | [[Firefox2/StatusMeetings/2006-02-28|next week>>]]</small>


= In Attendance =
= In Attendance =
 
autonome, axel, beltzner, ben, brettw, bsmedberg, darin, gavin, jhughes, markp, mconnor, schrep


= Agenda =
= Agenda =
Line 11: Line 11:
= Alpha 1 Status =
= Alpha 1 Status =
== Features ==
== Features ==
* Places infrastructure (performance, stability, toolbar drag & drop)
* '''Places infrastructure (performance, stability, toolbar drag & drop)'''
* Undo Close Tab
** ben: turned it on, turned it off again
* Tab Overflow
** ben: eight issues remaining, some small, some more significant; wary of not getting at least a week's worth of nightlies before shipping the alpha. Quick triage showed that there are 4-5 things that can be fixed within 24 hours or so, and another 4 that are more elaborate.
* Extension Blacklisting
** brett: a bunch of performance things can be fixed this week, and we've got a fix for some of the character loss. Haven't looked at the file size issue yet. I have some ideas how to fix the journal corruption bug.
* Extension Dependencies
*** schrep: how many of these issues were identified as a result of turning it on?
* Search Plugin Format Changeover (with sherlock import)
*** ben: a lot of it was regression discovery
* Spell-As-You-Type (english only)
*** brettw: some of it was that we knew performance was bad, so it's a little surprising that one of the reasons we turned it off was related to that (specifically the pageload time and perhaps the file size)
* Instrumentation Infrastructure
** schrep: so, net-net on time to resolve known issues before we can turn it back on?
* RSS parser
*** ben: I'm hesitant to say anything or speak for brettw, so I don't know. It depends on what content you want to have for alpha1.
* RSS content detection (?)
*** annie: I would rather see the UI tweaks go in first
*** ben: at the very least, regardless of A1/A2 targeting, it needs to be turned on for nightly testing ASAP.
*** beltzner: I think that it's very useful to have the backend changes in place for Alpha 1 if it's going to be a developer preview, and to let the UI change radically for the second alpha which we can open up to a wider range
** schrep: do we think we can get it turned back on in nightlies by next week?
*** brettw: yes, although I haven't looked at the journalling stuff
** schrep: so, reading backwards, soonest we could do A1 is Fri, Mar 3rd, assuming we put Places on early next week. But this date isn't a high confidence date.
*** brettw: any reason we can't get Places turned back on thursday morning?
*** annie: does it make sense to wait for a11y or l10n?
*** schrep: doesn't seem to if what we're saying is that the UI will change dramatically.
 
* '''Undo Close Tab'''
** ready for review
* '''Tab Overflow'''
** work in progress, eta Thursday
* '''Extension Blacklisting'''
** ready
* '''Extension Dependencies'''
** ready
* '''Search Plugin Format Changeover (with sherlock import)'''
** needs review from ben/mconnor, but ready otherwise
* '''Spell-As-You-Type (english only)'''
** not ready; been bogged down with Places work
* '''Instrumentation Infrastructure'''
* '''RSS parser'''
* '''RSS content detection (?)'''


== Blockers ==
== Blockers ==
Line 26: Line 50:
** currently set at 1.6a, should it be 2.0a?
** currently set at 1.6a, should it be 2.0a?
** beltzner needs to file patch to set branding to "Bon Echo"
** beltzner needs to file patch to set branding to "Bon Echo"
** need to flip switch on branch tinderboxen to use unofficial branding once Bon Echo change lands


== Release Requirements ==
== Release Requirements ==
* time requirements?
* Typical RC/Beta release is 4 business days (includes time for packaging, basic smoke testing, and configuring the update channels).


= Status Updates =
= Status Updates =
== Places ==
== Places ==
* A2/B1 list is growing, needs to be rebalanced to create good estimates
* '''action:''' set up meeting for late next week (ben, schrep, mconnor?) to reset milestone targets and get solid date estimates?
* UI documentation is being updated on the wiki and should be finalized by the end of the week


== Tabbed Browsing ==
== Tabbed Browsing ==
''mconnor will update shortly''
* Undo Close Tab will be posted for review shortly
* Tab overflow is in progress, spec done, will have patch by Thursday at the latest
* Will blog browsermessage API changes by the end of the week


== Extension Manager Enhancements ==
== Extension Manager Enhancements ==
Line 41: Line 74:
* Extension Update Notification - need to rethink the how we are going to provide notification - on startup is problematic due to requiring a check for only items that haven't been notified in a previous notification (e.g. avoiding notification on each startup). [https://bugzilla.mozilla.org/show_bug.cgi?id=307358 Bug 307358]
* Extension Update Notification - need to rethink the how we are going to provide notification - on startup is problematic due to requiring a check for only items that haven't been notified in a previous notification (e.g. avoiding notification on each startup). [https://bugzilla.mozilla.org/show_bug.cgi?id=307358 Bug 307358]
* Extension Manager UI - if I have time I am planning on a few changes to the ui. Will get with beltzner.
* Extension Manager UI - if I have time I am planning on a few changes to the ui. Will get with beltzner.
* rob_strong: we might not want to use preferences to control the blacklist as a malicious extension could simply override that preference
** ben: yeah, no matter where you keep that, I'm guessing that an extension could overwrite it
** schrep: so would you want to not have it configurable at all?
** rob_strong: I'm not sure if locked prefs work anymore or not, or a config file (that idea doesn't seem right, though). It's just something to keep in mind.


== Installer ==
== Installer ==
Line 51: Line 88:
**Are parameters hardcoded in the search plugin file sufficient for a1?
**Are parameters hardcoded in the search plugin file sufficient for a1?
* discuss Namespace/OpenSearch-support (Axel)
* discuss Namespace/OpenSearch-support (Axel)
** axel: do we want to avoid the opensearch namespace?
** mconnor: this is an internal format only
** bsmedberg: why does it matter?
** axel: it matters because searchplugins will tend to make errors one way or another; the question is how strict we do the parsing. I don't think we shouldn't be mixing namespaces for no good reason.
** bsmedberg: any reason this can't be brought up offline w/gavin as a bug or discussion on the wiki? this doesn't seem like an issue for this larger group.


== Visual Refresh ==
== Visual Refresh ==
* updated wiki documentation with requirements
* opening up discussion via blog entries and posts in dev-apps-firefox@lists.mozilla.org this week


== Platform Uplift ==
== Platform Uplift ==
* SVG <code>textPath</code> has a patch for the branch in [https://bugzilla.mozilla.org/show_bug.cgi?id=327539].  Need to figure out what the test plan looks like, but it looks like we're in good shape here.
* SVG <code>textPath</code> has a patch for the branch in [https://bugzilla.mozilla.org/show_bug.cgi?id=327539].  Need to figure out what the test plan looks like, but it looks like we're in good shape here.


Line 63: Line 106:


== Inline Spell Check ==
== Inline Spell Check ==
* licensing issues still open:
** english is being shipped with thunderbird, so it should be fine
** l10n are GPL or LGPL, so we can't ship without extra work
** axel: gerv is thinking about the topic as well


== Instrumentation / Exit Surveys ==
== Instrumentation / Exit Surveys ==
* Decided on XML data format with bzip2 compression for uploading user event logs
* Client and server work ongoing
* Tracking bug for enabling feature in alpha 2: https://bugzilla.mozilla.org/show_bug.cgi?id=328064


== Session Saver ==
== Session Saver ==
* Using a modified JS XPCOM service from the CrashRestore extension, working on getting it hooked up to bon echo.
* Using a modified JS XPCOM service from the CrashRestore extension, working on getting it hooked up to bon echo.


== Branding & Update Systems ==
== Branding & Update Systems ==
no update


== RSS ==
== RSS ==
no update


== Offline mode / better use of cache ==
== Offline mode / better use of cache ==
Christian suggested a better overall solution for {{bug|189570}}, but I may still go with my solution for now.  I plan on landing something this week.  --Darin


== Anti-Phishing ==
== Anti-Phishing ==
* darin: fritz only has three weeks left so we're looking to move on this sooner rather than later
** beltzner: we should make sure cbeard gets in touch with you before we decide what goes in the product, as we're looking at a variety of solutions and priorities
** darin: sure, but there's no point in not landing this on trunk now
** bsmedberg: absolutely, that's the right way to go
** beltzner: I didn't mean to say that it wasn't, just that I felt that you should know that cbeard has issues around this and you should talk to him
** darin: OK, well, get him to get in touch with us sooner rather than later, since I don't see why we can't do this in parallel
** '''action:''' cbeard to get in touch with darin


== EULA ==
== EULA ==
no update


== Performance ==
== Performance ==
no update


= Other Business =
= Other Business =
* darin: there is some work being done for CJK issues by jshin (Junshik Shin) that might be available for Alpha 2.  See {{bug|162361}}.
Confirmed users, Bureaucrats and Sysops emeriti
3,599

edits