Confirmed users, Bureaucrats and Sysops emeriti
3,599
edits
Firefox2/StatusMeetings/2006-02-21: Difference between revisions
Jump to navigation
Jump to search
Firefox2/StatusMeetings/2006-02-21 (view source)
Revision as of 19:26, 21 February 2006
, 21 February 2006no edit summary
No edit summary |
|||
| Line 2: | Line 2: | ||
= In Attendance = | = In Attendance = | ||
autonome, axel, beltzner, ben, brettw, darin, gavin, 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)''' | ||
** ben: turned it on, turned it off again | |||
** ben: eight issues remaining, some small, some more significant; weary 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. | |||
** 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. | |||
*** schrep: how many of these issues were identified as a result of turning it on? | |||
*** ben: a lot of it was regression discovery | |||
*** 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) | |||
** schrep: so, net-net on time to resolve known issues before we can turn it back on? | |||
*** 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. | |||
*** 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 | * Undo Close Tab | ||
* Tab Overflow | * Tab Overflow | ||
| Line 32: | Line 50: | ||
= 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 == | ||