Mossop
Current Status - Posted on 2010-03-12
Done:
- Wired up installs and blocked installs from webpages
- Converted the xpinstall test suite to work with the new APIs
- Started preparing the project branch for performance testing
Next:
- Finish support for extensions that don't need restarts
- Personas and plugins support
- Background auto-updates
- Convert the old EM test suite to the new APIs
- Make sure the API docs are in sync with the code
- Make a list of things not yet implemented for QA
- Put together a plan for a trunk landing
Older Posts
Member of Projects
Team Posts
Posted on 2010-03-15
sdwilsh
Done:
A bunch of reviews and work on I/O reduction goal.
Next:
- More reviews
- Start work on an IndexedDB prototype
- Land bug 536978 (async cookie writes) for Q1 goal.
Posted on 2010-03-12
ddahl
Done:
DevTools status.
The current console patches are found on bug 545266 and bug 546708 - also try builds will start once things are actually usable - I hope end of next week. It turns out that trying to attach (and keep attached) an arbitrary object on a nsIDOMWindow is a it of a pain - from outside the window's constructor. sicking told me about his patch for detecting new windows (before content scripts run) and attaching objects to them: bug 549539 - which landed late today. Yay. With this patch on trunk it should be trivial now to detect window construction and attach a console.
Whoops, forgot to mention that the console does log to the output, but once you navigate away, the console object attached to the window is destroyed.
I gave up on the html document approach for now, I think it can be worked out, just was spending too much time on it. For now, it is just a XUL vbox element where the output is appended to.
Next:
Work with the new window detection hooks to implement the observer that keeps window consoles re-appearing. Every load of the browser creates a new nsIDOMWindow - news to me, anyway.
Posted on 2010-03-12
Mossop
Done:
- Wired up installs and blocked installs from webpages
- Converted the xpinstall test suite to work with the new APIs
- Started preparing the project branch for performance testing
Next:
- Finish support for extensions that don't need restarts
- Personas and plugins support
- Background auto-updates
- Convert the old EM test suite to the new APIs
- Make sure the API docs are in sync with the code
- Make a list of things not yet implemented for QA
- Put together a plan for a trunk landing
Posted on 2010-03-11
jdm
Done:
New patch (hopefully final) up for review for remoting chrome registry (bug 542907) Static analysis for bug 551286 (NS_FINAL attribute for functions) Various investigations into multiprocess Jetpack design
Next:
More Jetpack investigation - properties/restrictions of evalIntoSandbox and scope, CPOWs
Posted on 2010-03-08
mnandigama
Done:
Looked at the regression ranges [ Regbugfixes/(Genbugfixes+Regbug_fixes) ] by component and by top 10 files [ by total bug fixes ] in each component and by overall top ten files [ by total bug fixes ] to identify any SPC spread exceptions.
Identified a bunch of source files that are part of 1.9.1 and no longer exist in trunk. What would have happened to the corresponding tests. Are they refactored ? retired or running as usual. If they are running as usual, then are they still testing what they are supposed to test ? In order to answer this question, I need to generate test case to source file mapping which would be many to many using modified code coverage test run scripts.
Next:
Design a test routine that executes tests one by one and collects test case to source file mapping.
Posted on 2010-03-02
michal
Done:
bug 537164 - e10s HTTP: caching bug 549241 - Channel classifier
Next:
bug 537164 - e10s HTTP: caching bug 549241 - Channel classifier bug 536317 - e10s HTTP: implement Cancel bug 486199 - SCTP
Posted on 2010-03-01
honzab
Done:
Made some progress on sec UI for e10s, but still in the design phase Bug 543726 HTML5: test_foreign.html fails Some e10s discussions
Next:
Bug 534667 app cache for e10s sec UI
Posted on 2009-12-22
Unfocused
Done:
- Got first review of Tab matches in Awesomebar.
- Started work on new Extension Manager UI.
Next:
- Tab matches in Awesomebar: review, rinse, repeat.
- Building Extension Manager UI prototype and hooking it up to the new API
Posted on 2009-10-30
dietrich
Done:
Status update: http://autonome.wordpress.com/2009/10/31/firefox-startup-performance-weekly-summary-8/
Posted on 2009-10-19
mconnor
Done:
- Short week due to Thanksgiving/travel to Bay Area.
- Labs offsite!
- Some work on Weave Firefox UI
- Dealing with perceived sec implications of Personas integration in Firefox
Next:
- Finish and land new Weave UI for Firefox for pre2
- Fixing followups
- Fennec UI evolution