<< How To Drive Away Contributors | The roads I take... | 47 >>

Weekly Status Report, W08/2010

Here's a summary of SeaMonkey/Mozilla-related work I've done in week 08/2010 (February 22 - 28, 2010):

Build Infrastructure And Automated Tests:
The new Mac machines are here and working now, I integrated them into the build pool and then requested some Parallels VM restructuring.
Phong from Mozilla IT already had set up the new minis for us and replaced our previous older mini with one that has 1GB of RAM so it can process build symbols correctly. He also performed that restructuring of VMs on Parallel so that we now have 5 build machines on all three primary platforms. Thanks a lot for all that, this made us finally have the power to run everything we need on trunk and one branch (machines for a second release branch have been requested).
With all those machines working well, we could finally turn on all test suite for SeaMonkey trunk debug builds. Test runs show up on the SeaMonkey tinderbox page but many of them show failures. We'll need to work on getting that cleared up, even if those are shared or platform tests. We probably need to take care of getting fixes ourselves, platform people usually are satisfied when Firefox tests pass but willing to take patches that other apps pass as well.
We're failing on many mailnews tests when executing them from the tests packages as told before, I tried to do a patch by using more standard directories to put test files.
Additionally, I worked with Alice from Release Engineering to get graphs server posting moved to production and it's done now!
Places:
On my local system only, I did some more work on places bookmarks support, and I now have the personal bookmarks toolbar as well as both the main bookmarks menu and the toolbar menubutton showing correctly and calling up saved bookmarks, live bookmarks work and even microsummaries should. A number of the context menu commands still need some work, and I have no support whatsoever for adding or managing bookmarks yet (with the exception of toolbar/menu drag and drop). And then, the files probably need a lot of cleanup, most of them are just directly copied from Firefox with just minor modifications.
I'm starting to wonder if and how to split up that work into smaller patches though as the work starts to get quite large, a diffstat for the current patch says "30 files changed, 13129 insertions(+), 111 deletions(-)" and I obviously haven't removed any of the old code yet.
While on the topic of places, I decided to also port some improvements from Firefox places code over to the history places stuff we already have in SeaMonkey. That's also not a small patch (62KB), but with 3 files changed, 631 insertions(+), 507 deletions(-) it's much more manageable for review, I hope, and it already had it's first rough pass of that but needs some answers from places developers as well to get in.

Services.jsm:
Gavin introduced Services.jsm to toolkit this week, and as I think this is a very welcome improvement for reducing code complexity, I did a patch for starting to use it in SeaMonkey right away. The patch is really just a start, but with adding 119 lines and removing 210 (somewhat clouded by breaking some previously too long lines at 80 characters) it shows the direction we're going there: an overall decrease of code lines - and at the same time better understandable code.
See my two favorite examples from that patch:

-  const kWindowMediatorContractID = "@mozilla.org/appshell/window-mediator;1";
-  const kWindowMediatorIID = Components.interfaces.nsIWindowMediator;
-  const kWindowMediator = Components.classes[kWindowMediatorContractID]
-                                    .getService(kWindowMediatorIID);
-  var lastPrefWindow = kWindowMediator.getMostRecentWindow("mozilla:preferences");
+  var lastPrefWindow = Services.wm.getMostRecentWindow("mozilla:preferences");

-  var observerService = Components.classes[kObserverServiceProgID]
-                                  .getService(Components.interfaces.nsIObserverService);
-  observerService.removeObserver(offlineObserver, "network:offline-status-changed");
-  var prefService = Components.classes["@mozilla.org/preferences-service;1"];
-  prefService = prefService.getService(Components.interfaces.nsIPrefService);
-  var prefBranch = prefService.getBranch(null);
-  prefBranch = prefBranch.QueryInterface(Components.interfaces.nsIPrefBranch2);
-
-  prefBranch.removeObserver("network.proxy.type", proxyTypeObserver);
+  Services.obs.removeObserver(offlineObserver, "network:offline-status-changed");
+  Services.prefs.removeObserver("network.proxy.type", proxyTypeObserver);

Of course, a Components.utils.import("resource://gre/modules/Services.jsm"); has been added at the top level before all those calls.

German L10n:
I could get the German language pack listed on the Dictionaries & Language Packs page of the SeaMonkey Add-Ons website.
Various Discussions:
Fixing FTP file upload, How To Drive Away Contributors, go for Gecko 1.8.1.24 and SeaMonkey 1.x EOL-release, web form management, improvements for "human-readable" pushlog feeds, privacy policies, forms management, Mozilla communication channels, etc.

Could make some good progress this week, and build system porting is also progressing a lot, which is really good to see. I hope other SeaMonkey 2.1 work is also progressing so that we can make this a really good release. Meanwhile, a second alpha from the Mozilla 1.9.3 platform is being made, so we hopefully have something to base on once we have some new code to test in an alpha of our own.

Beitrag geschrieben von KaiRo und gepostet am 1. März 2010 17:36 | Tags: L10n, Mozilla, SeaMonkey, Status | 1 Kommentar | TrackBack

Kommentare

Autor	Beitrag
KaiRo Webmaster	Yes, 1.1.19 will mark the end of line - actually the announcement will mainly be EOL and the new release that fixes many but not all security problems with the previous 1.x releases. The only version that fixes all known issues is the current 2.0.x release. I have stopped nightlies because of that EOL. We need to do this before Thunderbird for multiple reasons - one being that we ship code that is different to Thunderbird (mostly in the browser) and doesn't get any security updates any more because nobody cares to port those fixes. If we can't ship secure releases from that branch, we should better not ship any. And the build machines for that branch are quite old and living in my private basement, they should really be turned off... 03.03.2010 23:21

Autor

Beitrag

KaiRo

Webmaster

Yes, 1.1.19 will mark the end of line - actually the announcement will mainly be EOL and the new release that fixes many but not all security problems with the previous 1.x releases. The only version that fixes all known issues is the current 2.0.x release.

I have stopped nightlies because of that EOL. We need to do this before Thunderbird for multiple reasons - one being that we ship code that is different to Thunderbird (mostly in the browser) and doesn't get any security updates any more because nobody cares to port those fixes. If we can't ship secure releases from that branch, we should better not ship any. And the build machines for that branch are quite old and living in my private basement, they should really be turned off...

03.03.2010 23:21

Kommentar hinzufügen