Weekly Status Report, W02/2010

Here's a summary of SeaMonkey/Mozilla-related work I've done in week 02/2010 (January 11 - 17, 2010):

• Releases:
  SeaMonkey 2.0.2 was released on Monday, mainly fixing a Windows mailcompose freeze which was a regression from 2.0.1 work. The previous 2.0.2 scheduled for early February was renamed to 2.0.3 and moved to the middle of that month.
• Build Infrastructure:
  I finally attacked the problem of L10n nightlies not being triggered and for that moved right over to mirroring the Firefox setup as closely as possible. After fixing a glitch from some wrong variable-repurposing for WinCE build work, it was a success in that our new config allows us to go for things like split test cycles much more easily and that L10n nightlies are being produced, but I needed to split L10n nightly updates into a different bug and do some more work on that - and we're not completely there yet.
  Also, the release automation bustage fix found with 2.0.2 work could be checked in, as well as the switch of release automation to pulling chatzilla from hg, which I now found time to write a patch for.
• SeaMonkey L10n:
  I finally came around to activating Italian ChatZilla and venkman, and Ukrainian SeaMonkey.
  As said above, work is going on for L10n nightly updates - right now, everything is actually working except that a wrong patch is being written into the snippets and so no update can be installed, even though builds know that it's available. I'm working on fixes for that (needs work across three Mercurial repositories).
• German L10n:
  To have something for reasonably testing the L10n building updates on trunk, I wanted German to build alright, so I went in and finally updated ChatZilla and venkman localizations, and while I was at it, DOM inspector and SeaMonkey as well. I also did small updates to DOM and security to sync them to current trunk development, but toolkit still needs a bit more work to be green on trunk.
• Various Discussions:
  Add-on compatibility center, new machines, comm-central policy for requiring tests, plans or no plans for platform releases, Lightning 1.0 Beta 1 release, external linkage for mailnews, Manifesto and privacy, profile management future, KompoZer and SeaMonkey, etc.

Work is definitely picking up, and I've also started trying the Mozilla Status Board tool, which will not replace but be an addition to my updates here - with the benefit of having a section of what I'm planning to do next. And my list of "next" items was quite large last week, I'll probably need to keep a few on that list this time as well...