Echoing Beltzner's request from before:
In preparation for this meeting, all team leads and drivers should look through this list and ensure that they've made blocking decisions on the outstanding blocker nominations:
Additionally, they should be prepared to discuss the status of all the blockers on this list:
General Agenda:
* Planning for the next release of 1.9.2
* discuss upcoming major changes landing on mozilla-central
* Status updates on feature development (both front-end and platform)
* Identifying areas of code risk for upcoming milestones
* Discussion of security review impacts, standards/spec compliance
work, internal and external dependencies
Meeting Details:
* Agenda: https://wiki.mozilla.org/Platform/2009-12-01
* Tue, Dec 1, 11:00 am PST
* 650-903-0800 x92 Conf# 8605 (US/INTL)
* 1-800-707-2533 (pin 369) Conf# 8605 (US)
* join irc.mozilla.org #planning for back channel
Sincerely,
Damon
> Additionally, they should be prepared to discuss the status of all the blockers on this list:
>
> https://bugzilla.mozilla.org/buglist.cgi?quicksearch=ALL%20-resolution:dup,wont,inv%20flag%3Ablocking-firefox3.6%2B%2Cblocking1.9.2%2B%20-status1.9.2:fixed,unaffected,wontfix
Actually, this list is more accurate (only counts bugs in code areas, discards bugs marked "WORKSFORME"):
That's 40 or so bugs, or slightly over 20 if we don't count the ones marked with "fixed-in-tracemonkey" or "crashkill-outreach/thirdparty" in the status whiteboard:
We should know where we stand on each of these in terms of ETA.
We should also be at zero in the nomination queue in advance of the meeting. That query is here:
cheers,
mike