Platform/2009-06-23: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
Line 2: Line 2:


=== Notices / Schedule ===
=== Notices / Schedule ===
* '''[[Releases/Firefox 3.0.12|Firefox 3.0.12]]'''
'''[[Releases/Firefox 3.0.12 |Firefox 3.0.12]]'''
** missed code freeze
* '''Please''' work on your blockers
** please work on [https://bugzilla.mozilla.org/buglist.cgi?keywords_type=nowords&keywords=fixed1.9.0.12+verified1.9.0.12&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=blocking1.9.0.12%2B&field1-0-0=flagtypes.name&type1-0-0=notsubstring&value1-0-0=approval1.9.0.12&order=map_assigned_to.login_name,bugs.bug_id your blockers]
* Currently have '''[https://bugzilla.mozilla.org/buglist.cgi?keywords_type=nowords&keywords=fixed1.9.0.12+verified1.9.0.12&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=blocking1.9.0.12%2B&field1-0-0=flagtypes.name&type1-0-0=notsubstring&value1-0-0=approval1.9.0.12&order=map_assigned_to.login_name,bugs.bug_id 26 blockers]''' that need patches
* Firefox 3.0.13 schedule and blocker list coming soon
* Code freeze scheduled for tonight!
 
* Reminder: All patches require approval on 1.9.0. Blockers do ''not'' have automatic approval


'''[[Releases/Firefox_3.5rc1|Firefox 3.5 RCs]]'''
'''[[Releases/Firefox_3.5rc1|Firefox 3.5 RCs]]'''

Revision as of 17:38, 23 June 2009

« previous week | index | next week »

Notices / Schedule

Firefox 3.0.12

  • Please work on your blockers
  • Currently have 26 blockers that need patches
  • Code freeze scheduled for tonight!
  • Reminder: All patches require approval on 1.9.0. Blockers do not have automatic approval

Firefox 3.5 RCs

  • rc1 released to beta channel early last week
  • rc2 released to beta channel and posted on web
  • will likely need an rc3 for very localized fixes (no additional qa cycle)
  • making a call on shipping at tomorrow's meeting

Blocker Report

Browser / Front End

  • Polish update: Firefox is 60% shiny (+2% change as some were set invalid)

pub?key=pMZGKUlD9NOPg4oJGs1CUMw&oid=1&output=image&foo=.png

pub?key=pMZGKUlD9NOPg4oJGs1CUMw&oid=3&output=image&foo=.png

Priority levels:

The polish priority is based on a combination of UI location / frequency / severity.

  • UI location: is the polish issue in the main interface, a secondary interface, or even deeper into our UI?
  • Frequency: how often the user is likely to encounter the issue?
  • Severity: when the user encounters the issue are they even able to notice it?

Here are general descriptions of the levels:

  • P1 - Polish issue that appears in the main window, or is something that the user may encounter several times a day.
  • P2 - Polish issue that is in a secondary interface, occasionally encountered, and is easily identifiable.
  • P3 - Polish issue that is in a secondary interface, occasionally encountered, or is not easily identifiable.
  • P4 - Polish issue that is rarely encountered, and is easily identifiable.
  • P5 - Polish issue that is rarely encountered, and is not easily identifiable.

GFX 1.9.1 Update

Layout Update

Content Update

Mac OS X Update

JS 1.9.1

General 1.9.1

Mobile 1.9.1 Update

Security

Electrolysis

Multiprocess tabs are very basically working! See cjones' video.

Stage I is almost complete. We're finishing up small tasks so that phase II can begin:

  • sub-protocols and protocol management (cjones)
  • removing the writable string buffers/ldscript/short-whcar hack (??)
  • integrate IPIDL into the build system (bsmedberg)
  • landing the code into the project repository, with basic review and TODOs clearly marked (bsmedberg)
  • working on Windows again (bent)
  • IPIDL and general IPC documentation (cjones)

Phase II is where we can begin parallel hacking of different subsystems. The immediate list:

  • networking (jduell)
  • global history... needs async history (sdwilsh)
  • docshell hookup, session history, and link targeting (bz)
  • preferences (bsmedberg)

Additional items to spin up as we get more comfortable.

Multi-process plugin work needs love. cjones got something hooked up, but the plugins are not drawing, and it needs a lot of fleshing-out (kinetik?)

Tree Management

Roundtable