The roads I take...

Here's a summary of SeaMonkey/Mozilla-related work I've done in week 17/2009 (April 20 - April 26, 2009):

• Download Manager:
  The new UI patch now is available in it's final, ready-for-checkin version on the bug!
• SeaMonkey Buildbots:
  common comm-central unit test class was checked in this week and also deployed to SeaMonkey testers, removing custom factory code from the config directory.
  In other news, we have now really fixed the leaks we still had from the extension manager datasource stuff on shutdown, so I could also decrease the leak thresholds for all tests to 0 - with the only exception of Windows mochitest-plain, where we still report a 200 byte leak, probably related to some plugin stuff.
• Bug Triage and Statistics:
  Reminded on the topic of bug triage, I wrote an updated post on triage targets including the idea of changing all bugs back to UNCONFIRMED that have no comments since the new SeaMonkey project began, and in a few months go and change all UNCONFIRMED bugs to EXPIRED that haven't had a comment for a number of months. This could potentially clean up our view of the SeaMonkey product on Bugzilla a lot.
  Inspired by that triage stuff, I thought it would be nice to see some numbers of the weekly "performance" of SeaMonkey in Bugzilla, and created bug statistcs on dev.seamonkey.at as described in my recent blog post.
  There's more interesting data that could be gathered, but it looks nice that in the week I created those stats, we had 14 new bugs reported while fixing 18 and closing 30 to other resolutions by triaging. Not only did we resolve more bugs than we got new ones reported, we also fixed more than those new reports!
• German L10n:
  Once again, some string updates and cleanups were needed to keep German L10n green, nothing too complicated here though.
• Various Discussions:
  GSoC project decisions, EV cert UI, test failures, mail account autoconfig work, SeaMonkey statistics, MozCamp Wien, Mac theme rework, Linux updater issue and fixes, Mozilla 1.9.2 and Tiger support, bmo workflow, etc.

Looking into those bugzilla statistics is quite interesting: For example, in April, 68 bugs have been reported so far in the SeaMonkey product, 67 have been resolved by triage (only one less than the new ones) and 41 bugs have been fixed in that period. Esp. the latter number perfectly tells that development is moving on - given that 7 of those have been ranked with "enhancement" severity, it's clear that this active development also means new stuff coming in for SeaMonkey 2 and not just fixes of problems, even though those account for the majority of fixes.

Can you make those numbers look even better at the actual end of the month or enable us to have a good start into May by those measures? Helping is as easy as triaging UNCONFIRMED bugs and either determining that they are valid (NEW) or resolving them to INVALID, WONTFIX, DUPLICATE, WORKSFORME, or INCOMPLETE if you can't confirm them (actual resolution depends on why you can't confirm them to be valid reports, of course)!