Platform/2010-01-19 - Revision history

Ehsan: /* Browser / Front End */

2010-01-27T19:25:09Z

Browser / Front End

← Older revision		Revision as of 19:25, 27 January 2010
Line 40:		Line 40:
	** Rob Strong's been looking at [http://blog.mozilla.com/rstrong/2009/12/23/firefox-javascript-component-startup-costs/ performance of various front end components], and has also started looking at a [http://blog.mozilla.com/rstrong/2010/01/08/status-update-week-of-18/ slate of improvements] to the way we handle updates.		** Rob Strong's been looking at [http://blog.mozilla.com/rstrong/2009/12/23/firefox-javascript-component-startup-costs/ performance of various front end components], and has also started looking at a [http://blog.mozilla.com/rstrong/2010/01/08/status-update-week-of-18/ slate of improvements] to the way we handle updates.
	** Marco landed the work in {{bug\|520165}} that moves history expiration off of the main thread, and in the process moved a bunch of C++ to JS and cleaned up a lot of the older Places code. This provides snappiness and shutdown performance benefits.		** Marco landed the work in {{bug\|520165}} that moves history expiration off of the main thread, and in the process moved a bunch of C++ to JS and cleaned up a lot of the older Places code. This provides snappiness and shutdown performance benefits.
	** Progress on a new Places query API ({{bug\|522572}}), and ~~it's~~ integration with Jetpack.		** Progress on a new Places query API ({{bug\|522572}}), and its integration with Jetpack.
	** Progress on Places queries in content pages ({{bug\|529605}}).		** Progress on Places queries in content pages ({{bug\|529605}}).
	** Started moving session restore to mozStorage ({{bug\|508740}}).		** Started moving session restore to mozStorage ({{bug\|508740}}).

Beltzner: /* Roundtable */

2010-01-20T18:53:53Z

Roundtable

← Older revision		Revision as of 18:53, 20 January 2010
Line 167:		Line 167:
	= Roundtable =		= Roundtable =
	* Plans for releases post-3.6? When do we need a 3.7 alpha?		* Plans for releases post-3.6? When do we need a 3.7 alpha?
			** we should catalog what's gone into mozilla-central since the 1.9.2 branch
			** need to identify which APIs have changed, and if non-API changing bits can be isolated for back porting
			** for each change, we should describe what the desired effect is, who should be asked to evaluate it for feedback, and what kind of feedback we're looking for
			** dbaron and damon will drive this effort
	* [http://antennasoft.net/robcee/2010/01/19/firebug-1-5-0/ Firebug 1.5.0 Released]		* [http://antennasoft.net/robcee/2010/01/19/firebug-1-5-0/ Firebug 1.5.0 Released]

Dietrich: /* Browser / Front End */

2010-01-19T22:38:54Z

Browser / Front End

← Older revision		Revision as of 22:38, 19 January 2010
Line 39:		Line 39:
	** Getting close to a UI for how to handle crashed plugins in a world with out of process plugins {{bug\|538910}}		** Getting close to a UI for how to handle crashed plugins in a world with out of process plugins {{bug\|538910}}
	** Rob Strong's been looking at [http://blog.mozilla.com/rstrong/2009/12/23/firefox-javascript-component-startup-costs/ performance of various front end components], and has also started looking at a [http://blog.mozilla.com/rstrong/2010/01/08/status-update-week-of-18/ slate of improvements] to the way we handle updates.		** Rob Strong's been looking at [http://blog.mozilla.com/rstrong/2009/12/23/firefox-javascript-component-startup-costs/ performance of various front end components], and has also started looking at a [http://blog.mozilla.com/rstrong/2010/01/08/status-update-week-of-18/ slate of improvements] to the way we handle updates.
			** Marco landed the work in {{bug\|520165}} that moves history expiration off of the main thread, and in the process moved a bunch of C++ to JS and cleaned up a lot of the older Places code. This provides snappiness and shutdown performance benefits.
			** Progress on a new Places query API ({{bug\|522572}}), and it's integration with Jetpack.
			** Progress on Places queries in content pages ({{bug\|529605}}).
			** Started moving session restore to mozStorage ({{bug\|508740}}).

	= GFX Update =		= GFX Update =

Jesse: /* Roundtable */

2010-01-19T19:31:22Z

Roundtable

← Older revision		Revision as of 19:31, 19 January 2010
Line 162:		Line 162:

	= Roundtable =		= Roundtable =
	* ~~Release plans~~?		* Plans for releases post-3.6? When do we need a 3.7 alpha?
	* [http://antennasoft.net/robcee/2010/01/19/firebug-1-5-0/ Firebug 1.5.0 Released]		* [http://antennasoft.net/robcee/2010/01/19/firebug-1-5-0/ Firebug 1.5.0 Released]

Joduinn: /* Tree Management */

2010-01-19T19:28:31Z

Tree Management

← Older revision		Revision as of 19:28, 19 January 2010
Line 156:		Line 156:
	* 100 new minis!		* 100 new minis!
	** 60 have been imaged with Windows XP, Windows 7, and OSX 10.5.8		** 60 have been imaged with Windows XP, Windows 7, and OSX 10.5.8
			** 40 more coming by mid-week
	** http://oduinn.com/2010/01/18/talos-recalibration-status-18jan2010/		** http://oduinn.com/2010/01/18/talos-recalibration-status-18jan2010/
			** will need downtime this week
			* Lorentz branch in progress -details in {{bug\|536188}}

	= Roundtable =		= Roundtable =
	* Release plans?		* Release plans?
	* [http://antennasoft.net/robcee/2010/01/19/firebug-1-5-0/ Firebug 1.5.0 Released]		* [http://antennasoft.net/robcee/2010/01/19/firebug-1-5-0/ Firebug 1.5.0 Released]

Rcampbell: /* Roundtable */

2010-01-19T19:28:15Z

Roundtable

← Older revision		Revision as of 19:28, 19 January 2010
Line 160:		Line 160:
	= Roundtable =		= Roundtable =
	* Release plans?		* Release plans?
			* [http://antennasoft.net/robcee/2010/01/19/firebug-1-5-0/ Firebug 1.5.0 Released]

Beltzner at 19:27, 19 January 2010

2010-01-19T19:27:30Z

← Older revision		Revision as of 19:27, 19 January 2010
Line 147:		Line 147:
	* Coordination meetings continue Wednesday, 1PM PT		* Coordination meetings continue Wednesday, 1PM PT

	=== Breakpad ===		= Breakpad =
	* DWARF Call Frame Information (CFI), needed to enable -fomit-frame-pointer optimization and required for stack traces at all on ARM (mobile):		* DWARF Call Frame Information (CFI), needed to enable -fomit-frame-pointer optimization and required for stack traces at all on ARM (mobile):
	** Linux DWARF support is complete, with full unit tests; Google has five patches awaiting review.		** Linux DWARF support is complete, with full unit tests; Google has five patches awaiting review.

Jimb: Add Breakpad section.

2010-01-19T19:26:20Z

Add Breakpad section.

← Older revision		Revision as of 19:26, 19 January 2010
Line 146:		Line 146:
	* Broke OOPP users with this morning's nightly, but we're respinning nightlies		* Broke OOPP users with this morning's nightly, but we're respinning nightlies
	* Coordination meetings continue Wednesday, 1PM PT		* Coordination meetings continue Wednesday, 1PM PT

			=== Breakpad ===
			* DWARF Call Frame Information (CFI), needed to enable -fomit-frame-pointer optimization and required for stack traces at all on ARM (mobile):
			** Linux DWARF support is complete, with full unit tests; Google has five patches awaiting review.
			** Minidump processor side support for CFI is complete and implemented for x86, with full unit tests. Not done for ARM, but that should be quick.
			** Symbol dumping work (final step) in progress, ETA this week or next.

	= Tree Management =		= Tree Management =

Beltzner: /* Platform-specific Support Update */

2010-01-19T19:21:08Z

Platform-specific Support Update

← Older revision		Revision as of 19:21, 19 January 2010
Line 57:		Line 57:
	** Apple should be releasing another Java update beta soon, which should have an updated NPAPI Java plugin (JavaPlugin2). We are hopeful that they'll ship something good enough to replace JEP by March. We'll be monitoring the situation closely.		** Apple should be releasing another Java update beta soon, which should have an updated NPAPI Java plugin (JavaPlugin2). We are hopeful that they'll ship something good enough to replace JEP by March. We'll be monitoring the situation closely.
	** So that we don't depend on Apple, Steven will begin porting the JEP to NPAPI ASAP. This should take 4-6 weeks of dedicated work. We'll abort the JEP port if/when we see a good enough Java plugin from Apple.		** So that we don't depend on Apple, Steven will begin porting the JEP to NPAPI ASAP. This should take 4-6 weeks of dedicated work. We'll abort the JEP port if/when we see a good enough Java plugin from Apple.

			* Rob Arnold is [http://robarnold.org/help-needed-with-aero-peek-tab-previews/ looking for help with Aero Peek] - if you are or know a good Windows API hacker, please take a look and see if you can contribute!

	= JS =		= JS =

Johnath: /* Browser / Front End */

2010-01-19T19:18:39Z

Browser / Front End

← Older revision		Revision as of 19:18, 19 January 2010
Line 35:		Line 35:
	= Browser / Front End =		= Browser / Front End =
	* Lots of awesome work being done on future-looking firefox work, including:		* Lots of awesome work being done on future-looking firefox work, including:
	** Tab matches in awesomebar (nearly done!)		** Tab matches in awesomebar (nearly done!) {{bug\|480350}}
	** New Extension Manager API work continuing, with parallel EM UI development as well.		** New [https://wiki.mozilla.org/Extension_Manager:API_Rewrite Extension Manager API] work continuing, with parallel [https://wiki.mozilla.org/Extension_Manager:UI_Update EM UI] development as well.
	** Getting close to a UI for how to handle crashed plugins in a world with out of process plugins		** Getting close to a UI for how to handle crashed plugins in a world with out of process plugins {{bug\|538910}}
	** Rob Strong's been looking at performance of various front end components, and has also started looking at a slate of improvements to the way we handle updates.		** Rob Strong's been looking at [http://blog.mozilla.com/rstrong/2009/12/23/firefox-javascript-component-startup-costs/ performance of various front end components], and has also started looking at a [http://blog.mozilla.com/rstrong/2010/01/08/status-update-week-of-18/ slate of improvements] to the way we handle updates.

	= GFX Update =		= GFX Update =

← Older revision		Revision as of 19:25, 27 January 2010
Line 40:		Line 40:
	** Rob Strong's been looking at [http://blog.mozilla.com/rstrong/2009/12/23/firefox-javascript-component-startup-costs/ performance of various front end components], and has also started looking at a [http://blog.mozilla.com/rstrong/2010/01/08/status-update-week-of-18/ slate of improvements] to the way we handle updates.		** Rob Strong's been looking at [http://blog.mozilla.com/rstrong/2009/12/23/firefox-javascript-component-startup-costs/ performance of various front end components], and has also started looking at a [http://blog.mozilla.com/rstrong/2010/01/08/status-update-week-of-18/ slate of improvements] to the way we handle updates.
	** Marco landed the work in {{bug\|520165}} that moves history expiration off of the main thread, and in the process moved a bunch of C++ to JS and cleaned up a lot of the older Places code. This provides snappiness and shutdown performance benefits.		** Marco landed the work in {{bug\|520165}} that moves history expiration off of the main thread, and in the process moved a bunch of C++ to JS and cleaned up a lot of the older Places code. This provides snappiness and shutdown performance benefits.
	** Progress on a new Places query API ({{bug\|522572}}), and ~~it's~~ integration with Jetpack.		** Progress on a new Places query API ({{bug\|522572}}), and its integration with Jetpack.
	** Progress on Places queries in content pages ({{bug\|529605}}).		** Progress on Places queries in content pages ({{bug\|529605}}).
	** Started moving session restore to mozStorage ({{bug\|508740}}).		** Started moving session restore to mozStorage ({{bug\|508740}}).