Confirmed users, Bureaucrats and Sysops emeriti
3,599
edits
Firefox2/StatusMeetings/2006-04-11: Difference between revisions
Jump to navigation
Jump to search
Firefox2/StatusMeetings/2006-04-11 (view source)
Revision as of 18:38, 11 April 2006
, 11 April 2006no edit summary
(→Agenda) |
No edit summary |
||
| Line 17: | Line 17: | ||
= Bon Echo Alpha 2 = | = Bon Echo Alpha 2 = | ||
* proposed release for May 9th, code freeze for May 5th | * proposed release for May 9th, code freeze for May 5th | ||
** ben: should we talk about this in context of A3? | |||
*** beltzner: I don't think whether or not we do A3 should affect A2's date | |||
*** shaver: I think it might; if we do an A3 it might slip or slide the A2 content | |||
* tracking [[Firefox2/Requirements|against requirements]] | * tracking [[Firefox2/Requirements|against requirements]] | ||
* | ** rstrong: extension locales might not make it | ||
* ' | ** shaver: need timelines for offline storage, timer loop stuff | ||
** ben: session restore is there but need to watch Tp/Ts | |||
** ben: places needs to consider an A3 to be feature complete | |||
** ben: RSS UI will probably not make an A2 | |||
** bsmedberg: new installer will require some release/build engineering time to get things working properly | |||
* what platform pieces are being targetted? | |||
** shaver: event loop pieces, canvas context stuff (maybe, vlad's overburdened with timer fixes and offline storage as well) | |||
= Developer Roundtable = | = Developer Roundtable = | ||
| Line 40: | Line 49: | ||
=== Bookmarks and History: Places === | === Bookmarks and History: Places === | ||
* Making good progress: | |||
Making good progress: | ** 58 a2 issues open... annie 14 brettw 14 ben 10 joe 13 pam 3 | ||
** annie 19 brettw 13.5 beng 16 joe 15 | |||
** focusing on feature complete & major "functionality broken" bugs. | |||
* schrep: what's a user with A2 going to see difference-wise from A1 in terms of places | |||
** ben: some new functionality, better performance, the UI polish in terms of presentation might not be there; how's search gonna be? | |||
=== User Experience: Tabbed Browsing === | === User Experience: Tabbed Browsing === | ||
''mconnor to fill this bit in'' | |||
* myk: how's the new browsermessage stuff? | |||
** mconnor: first review is done, it's pretty cool, gonna get enn to do a second pass on that | |||
=== User Experience: Session Restore === | === User Experience: Session Restore === | ||
* Patch available for testing at [https://bugzilla.mozilla.org/show_bug.cgi?id=328162 bug 328162] | * Patch available for testing at [https://bugzilla.mozilla.org/show_bug.cgi?id=328162 bug 328162] | ||
* Currently working on fixing Ts regression | * Currently working on fixing Ts regression | ||
=== User Experience: Spell Check === | === User Experience: Spell Check === | ||
* a few pieces of work yet to be done; might increase file size | |||
* '''action:''' brettw to file bugs and get them targetted at A2 | |||
=== User Experience: Microsummaries === | === User Experience: Microsummaries === | ||
* Landed first patch: [https://bugzilla.mozilla.org/show_bug.cgi?id=333052 bug 333052], which makes the bookmarks toolbar observe the "bookmarks/generatedTitle" annotation. When the microsummary service sets or updates that annotation for a particular bookmark, the toolbar now uses the content of the annotation as the bookmark's label. | |||
Landed first patch: [https://bugzilla.mozilla.org/show_bug.cgi?id=333052 bug 333052], which makes the bookmarks toolbar observe the "bookmarks/generatedTitle" annotation. When the microsummary service sets or updates that annotation for a particular bookmark, the toolbar now uses the content of the annotation as the bookmark's label. | * Currently working on patch implementing microsummary service. | ||
Currently working on patch implementing microsummary service. | |||
=== Feeds: Parser === | === Feeds: Parser === | ||
* Robert sayrer needs to address peterv review feedback and get sr asap. | |||
Robert sayrer needs to address peterv review feedback and get sr asap. | * Needs to complete feed parser js component (beng reviewing) | ||
* '''action:''' mconnor to speed SR for this piece | |||
Needs to complete feed parser js component (beng reviewing) | |||
=== Feeds: UI === | === Feeds: UI === | ||
* Blocked by prereq (feed parser) | |||
Blocked by prereq (feed parser) | |||
=== Extension Manager: UI === | === Extension Manager: UI === | ||
| Line 77: | Line 86: | ||
=== Extension Manager: Locale Packs === | === Extension Manager: Locale Packs === | ||
* might not make A2 | |||
=== Search: UI === | === Search: UI === | ||
* Search engine manager patch to be submitted this week | * Search engine manager patch to be submitted this week | ||
** ben and beltzner brought up a few things that gavin didn't have on his radar | |||
** '''action:''' beltzner to file bug about moving the search drop-down selector to the right hand side of the search bar | |||
** Got sidetracked by some 1.0.8 regressions | ** Got sidetracked by some 1.0.8 regressions | ||
=== Search: Plugin Format === | === Search: Plugin Format === | ||
*Little bug fixes and cleanup has been reviewed and will land soon | * Little bug fixes and cleanup has been reviewed and will land soon | ||
*Format changes delayed until b1 | * Format changes delayed until b1 | ||
=== Distribution: Installer === | === Distribution: Installer === | ||
| Line 91: | Line 103: | ||
=== Distribution: Channel Support === | === Distribution: Channel Support === | ||
* darin: anything | |||
=== Infrastructure: Performance === | === Infrastructure: Performance === | ||
* Are there SVG performance improvement opportunities for Fx2? Starting to get pokes from people building SVG-heavy applications (mapping), etc. about timeline for improvements (Fx2 vs Fx3). | * Are there SVG performance improvement opportunities for Fx2? Starting to get pokes from people building SVG-heavy applications (mapping), etc. about timeline for improvements (Fx2 vs Fx3). | ||
* Did the compiler-switch conversation happen offline? | * Did the compiler-switch conversation happen offline? | ||
=== Infrastructure: Platform Uplift === | === Infrastructure: Platform Uplift === | ||
* JS 1.7 to arrive by end of April ("or bust" per Brendan): generators, iterators, array comprehensions, let, block scope, destructuring assignment | * JS 1.7 to arrive by end of April ("or bust" per Brendan): generators, iterators, array comprehensions, let, block scope, destructuring assignment | ||
* Canvas interface and optimizations ([https://bugzilla.mozilla.org/show_bug.cgi?id=333177 bug 333177]): vlad needs to decide to land them on trunk first for baking prior to a2. Would be good to get 1.8+patch experimental builds up somewhere for canvas-developers to test. | * Canvas interface and optimizations ([https://bugzilla.mozilla.org/show_bug.cgi?id=333177 bug 333177]): vlad needs to decide to land them on trunk first for baking prior to a2. Would be good to get 1.8+patch experimental builds up somewhere for canvas-developers to test. | ||
| Line 107: | Line 117: | ||
* shaver: still concerned about getting the right hooks in place for extensions, esp. WRT Places, Session Saver, and notification area (if it happens). | * shaver: still concerned about getting the right hooks in place for extensions, esp. WRT Places, Session Saver, and notification area (if it happens). | ||
* 1.8.1 nomination triage meeting: is it scheduled? | * 1.8.1 nomination triage meeting: is it scheduled? | ||
** schrep: yes, we should just schedule it - you want to do a first pass and target that at the end of this week? | |||
** shaver: I'll do the first pass if you schedule the meeting | |||
=== Infrastructure: Instrumentation === | === Infrastructure: Instrumentation === | ||
| Line 117: | Line 129: | ||
= Other Business = | = Other Business = | ||
=== Alpha 3 === | |||
* ben: I've been moving bugs to B1 which would probably be good to fix before the beta cycle; they're not new features, but they'd be useful to get before alpha | |||
* schrep: that would push us into September for the schedule; if it's completing what we currently have planned, that's one thing, but if it's jamming a bunch of new stuff in there, that's a different issue. | |||
* ben: some of the work on the UI hasn't started yet (not even talking about tags) and in my experience the UI polish work often leads to new bugs | |||
* ??: I thought the approach of evaluating whether or not an A3 as we come up to A2 deadline was the best one to take; minimizes risk and slip | |||
* mconnor: afraid that if we add an A3, we'll end up with longer cycles in beta, and we'll end up adding more features and just delaying ship even further | |||
* myk: there's uncertainty with uSummaries, too, especially in terms of the available review resources | |||
* schrep: what would you be able to do differently now knowing that there might be an alpha3? | |||
** ben: I'd be able to prioritize work more accurately; it wouldn't change the work that people are doing today | |||
* consensus was to push towards A2 and re-evaluate closer to ship | |||