View source for Platform/2008-12-09

<small>[[Platform/2008-12-02|&laquo; previous week]] | [[Platform|index]] | [[Platform/2008-12-16|next week &raquo;]]</small>

=== Details ===
* Tuesday - 11:00am Pacific, 2:00pm Eastern, 19:00 UTC
* Mozilla Building S - &lt;script&gt; conference room
* 650-903-0800 or 650-215-1282 x92 Conf# 8605 (US/INTL)
* 1-800-707-2533 (pin 369) Conf# 8605 (US)
* irc.mozilla.org #shiretoko for backchannel

=== Notices / Schedule ===
* Please take a look at the feature list and get things missing added, and update status for things you own: [[Firefox3.1/Features#Gecko_1.9.1]]
* See [[Firefox3.1/Security|the security review schedule]] page to get your review scheduled ASAP!

'''[[Releases/Firefox_3.1b2|Beta 2]]'''
* we're done here

'''[[Releases/Firefox_3.1b3|Beta 3]]'''
* schedule tbd today in round table

'''Blocker Report'''
http://people.mozilla.org/~beltzner/images/2008-12-09-blocker-report.png

=== Firefox 3.1 Update ===
* [http://tinyurl.com/5vuco5 51 Firefox 3.1 blockers]
** [http://tinyurl.com/5z38vm 12 Blockers to be fixed for Beta 3 (P1)]
** [http://tinyurl.com/6xq62f 8 Blockers to be fixed for RC (P2)]
** [http://tinyurl.com/5tybjm 28 Untriaged blockers (will be triaged shortly)]
** [http://tinyurl.com/6o3pxt 3 P3-P5 blockers (may not be fixed)]

* Polish update: Firefox is 17% shiny
** 14 of 54 [http://tinyurl.com/5d5qwm easy polish bugs] fixed (whiteboard [polish-easy])
** 0 of 29 [http://tinyurl.com/6delb6 hard polish bugs] fixed (whiteboard [polish-hard])

=== GFX 1.9.1 Update ===
* [http://tinyurl.com/5xfmvp GFX blocking 1.9.1+]
* Linux dl fonts checked in on trunk; not on 1.9.1 yet
* 10 blockers to go, 6 blockers checked in on trunk but not checked in on 1.9.1

=== Layout 1.9.1 Update ===
* [http://tinyurl.com/6zjp33 Layout wanted1.9.1+]
* Current blocker counts:
** SVG 9
** Video/Audio 20
** "Layout proper" 22
** Some triage needed, mostly recently-filed fuzz bugs

=== Content 1.9.1 Update ===
* [http://tinyurl.com/5a8vc2 Content 1.9.1 Bugs]

=== JS 1.9.1 ===
* [http://tinyurl.com/5gmg8y JS 1.9.1 Bugs]
* Focusing on [https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=blocking1.9.1%20JS&sharer_id=20209 blockers]. From 60, down to 40-45, fixed about 20, added 5 or so.
* Merged with trunk as of saturday, reasonably stable
* Fixes for some systemic issues coming in, should prevent classes of correctness bugs.

=== Mobile 1.9.1 Update ===

=== General 1.9.1 Updates ===

=== Security ===

==== [[Firefox3.1/Security#Pending_Reviews|Security Reviews]] ====
<font color="red">'''Still outstanding / to be scheduled'''</font>
* Javascript Tracing
* native JSON 
* Clear Private Data (Johnath to schedule)
* HTML5 drag-and-drop (Dan Veditz to schedule)

'''Booked but not yet completed'''
* Private Browsing
* elliptical border-radius (to be reviewed by Dan and Jonas to see if a full on review is needed)

=== Roundtable ===
* enabling a11y tests in production.

* new l10n system now running on mozilla-central.
** will watch between now and friday
** plan to enable on mozilla-1.9.1 on friday; turn off bsmedberg's machines (with many thanks!)

* Polish update: Firefox is 17% shiny
** 14 of 54 [http://tinyurl.com/5d5qwm easy polish bugs] fixed (whiteboard [polish-easy])
** 0 of 29 [http://tinyurl.com/6delb6 hard polish bugs] fixed (whiteboard [polish-hard])

* BayCHI presentation [http://www.baychi.org/program/#1 Designing Google Chrome] is tonight at PARC

* Some fun queries about FIXED and fixed1.9.1:
** [http://tinyurl.com/5vybng 21 blockers] have been FIXED on trunk, but not yet fixed on 1.9.1 - please remember to double land!
** [http://tinyurl.com/6rn9dy 33 bugs] have been marked FIXED on trunk, have approval1.9.1+, but are not marked fixed1.9.1 ([http://tinyurl.com/6cgptn 2 of those] are checkin-needed)

* Setting Beta 3 schedule
** holiday time means we need to be cautious to ensure that people get patches up in time for reviews, etc
** first draft schedule (component leads to think about this, beltzner to get QA estimates and double check assumptions):
*** Jan 13 - code freeze
*** Jan 19 - QA start
*** Jan 26 - release
** goal will be to accelerate that schedule if possible, especially code freeze to QA start