Weekly Status Report, W17/2011

Here's a short summary of SeaMonkey/Mozilla-related work I've done in week 17/2011 (April 25 - May 1, 2011):

• Mozilla work / crash-stats:
  Looked into a bit of crash analysis, and mostly fixed my experimental explosive crash analysis, but not too much new was going on. The crashes on Trunk and Aurora had been mostly covered, but Aurora still has way too few users to be really useful.
  As the new Socorro version finally landed, we got some insight into its new features and I filed a bug on duplicates that Marcia observed.
• SeaMonkey Administrative Stuff:
  Tried to get more things moving forward to move my remaining responsibilities over to other people.
• SeaMonkey Search:
  Followed some review comments on my patch for linking Engine Manager in sidebar and prefs and should be able to get the main thing into 2.1 by avoiding the one hairy case.
• Data Manager:
  Reviewed a test patch after an addition of permissions to the default set made them fail.
• German L10n:
  I updated the German SeaMonkey website for 2.0.14 shipping and sent out announcements to German newsgroups.
• Various Discussions/Topics:
  User notification project, 5.0b1, unprompted updates for users of EOLed Firefox releases, installer fix for optional extensions, comm-2.0 and mailnews, the (in)significance of version numbers in the new Firefox process, Linux gcc 4.5 + PGO landing, MeeGo N900 DE, etc.

Still recovering from a cold, I kept that week pretty light, but good things are happening nonetheless - for example, SeaMonkey is getting really close to cutting 2.1 builds, which will be "release candidate" for the moment, of course, but we hope those can just be converted to the actual final release as-is!
Also, it more and more looks as if SeaMonkey will chime in with the rapid release process and produce small but fast updates in the future, which also should get exciting. That may mean that 2.2 could have almost no visible changes to 2.1, but it will contain all web-facing changes that come with Firefox 5, and we'll be able to ship it just like a normal update to 2.1, so that the vast majority of people will "just get it" automatically.