Weekly Status Report, W11/2011

Here's a summary of SeaMonkey/Mozilla-related work I've done in week 11/2011 (March 14 - 20, 2011):

• Mozilla work / crash-stats:
  Worked with the CrashKill team through the bugs for new reports I have filtered out and assigned some priorities for those in the group, so we can go over those with the Socorro team on the all-hands.
  Replied to and summarized feedback I got on what users want from Socorro, put all that onto a wiki page and started writing up some of my thoughts on prioritizing work.
  Regularly generated "explosiveness" reports locally and uploaded them, looking at some signatures it brought up leaded to some bugs reports and catching one or the other item that might have slipped our view usually.
  I also filed a bug on improving correlation reports as those currently externally generated reports have a few weaknesses that could be mitigated when fully integrating them into the actual system.
• Build System:
  I created a patch to make removed-files L10n-aware so we don't leave over locale files on updates.
  Another issue I had been thinking about for some time is installing built-in extensions into the profile, which will finally make the update story for ChatZilla, venkman and DOM Inspector a clean story. If a newer version is shipped in SeaMonkey, it will overwrite the version in the profile, if AMO offers a newer version (and the user doesn't have updates disabled), we'll update to that one.
  In addition, I did some reviews for patches from Callek on SeaMonkey build infrastructure.
  Oh, and I landed Edmund's patch for the removed-files updates we found after extensively testing updates to SeaMonkey 2.1 Beta 2 earlier - thanks for working on this one!
• Search Bar and OpenSearch Engine Manager:
  I created a bug and patch for backporting searchbar/enginemanager fixes to Firefox, so both sides profit from this work.
• Data Manager:
  Invested some time into integrating the forget function for web storage panel in Data Manager (so far untested) and also did some work on reacting to live changes, but that item is not so easy due to different data types in this one panel.
• Themes:
  Did some testing of LCARStrek for Firefox 4 in my new virtualbox Win7 installation, so that I can see how it behaves with the "Firefox button". Clearly needs some more work, as I thought.
• German L10n:
  One more update for trunk SeaMonkey changes, including my own searchbar and OpenSearch engine manager additions.
• Various Discussions/Topics:
  Firefox 4 RC respin, future release system for Firefox, SeaMonkey planning and build hardware, drivers for my new bleeding-edge hardware, Firefox 4 Mobile going for RC, MeeGo N900 DE team forming, potentially merging mobile-browser with mozilla-central, etc.

It's exciting times: Firefox 4 is being released tomorrow! This doesn't only mean the Mozilla project shipping a lot of the work that has been going on in the last year and more to the majority of users out there, it also means (due to a decision made today) that crash-stats will probably be processing more crash reports than ever before on a single day while this release actually should be more stable than its predecessors - and it also means that the platform SeaMonkey 2.1 builds upon is now officially regarded "stable" and "everything" for the project left to do is finishing up the work on the last SeaMonkey-specific pieces, ship Beta 3 and soon thereafter the release candidate that hopefully will just be converted to the actual final release!

Hmm, I'm almost out of breath after this last sentence (actually, just kidding) and still shivering of excitement. Let's cheer for tomorrow and for another great step in the Mozilla project!