Firefox3/StatusMeetings/2006-06-28: Difference between revisions
< Firefox3 | StatusMeetings
		
		
		
		Jump to navigation
		Jump to search
		No edit summary  | 
				No edit summary  | 
				||
| Line 30: | Line 30: | ||
** (memory image cache size changes caused Tp change from network, but not Tp2 from disk)  | ** (memory image cache size changes caused Tp change from network, but not Tp2 from disk)  | ||
** analyze how we do testing (change the page order to something that resembles a real user's patterns, start using real-world type profiles instead of clean profiles, update Tp set)  | ** analyze how we do testing (change the page order to something that resembles a real user's patterns, start using real-world type profiles instead of clean profiles, update Tp set)  | ||
** schrep to get things going  | |||
= Firefox 3 =  | = Firefox 3 =  | ||
* We need Firefox3 demands from Gecko as input into the Gecko 1.9 focus list  | |||
= Other Business =  | = Other Business =  | ||
= Any other business =  | = Any other business =  | ||
Latest revision as of 19:38, 28 June 2006
<< previous week | index | next week>>
Meeting Details
- 11:00am PDT (18:00 UTC)
 - Mozilla HQ, 1st floor conference table
 - +1 866 216 2181 (or +1 303 228 0514)
 - join irc.mozilla.org #granparadiso for backchannel
 
Agenda
- Gecko 1.9 Roundtable
 - Firefox 3
 - Any other business
 
Gecko 1.9 Roundtable
- Web Compatibility
- Need to get data; not yet actionable
 - Can look through known bugs that block compatability
 - Reporter tool
 - Add topsite-compat type keyword to bugzilla for bugs that are related to web compatability; maybe topsite-compat? flag, with ?/+/- system
 - List of Gecko deviations from standards (but those are often at odds with web compat)
 - Compare compat/standards behaviour to IE6/7/WebKit/Opera
 - Low-hanging web compat fruit only!
 - Maybe Jay to lead data collection; Vlad to talk to him
 
 
- Set focused goals for priority items
- Numeric goals for each item? (e.g. improve memory footprint by 10%, improve Tp by 20% etc.)
 - Compare numbers relative to other browsers, instead of coming up with an arbitrary (darin has some data) (bz says 30-50% slower than opera 10-50% slower than IE on DHTML perf test)
 - Get numbers for 1.0/1.5/2.0/3.0 - some are on MozillaTest, but for linux -- we need windows numbers
 - (memory image cache size changes caused Tp change from network, but not Tp2 from disk)
 - analyze how we do testing (change the page order to something that resembles a real user's patterns, start using real-world type profiles instead of clean profiles, update Tp set)
 - schrep to get things going
 
 
Firefox 3
- We need Firefox3 demands from Gecko as input into the Gecko 1.9 focus list