Weekly Status Report, W31/2012

Here's a short summary of Mozilla-related work I've done in week 31/2012 (July 30 - August 5, 2012):

• CSI:Mozilla / CrashKill:
  Followed the developments of getting daily jobs running in a stable fashion again on Socorro and trying to get stage to work reliably, as that now blocks shipping any new code to production.
  Flash 11.3 is still a hot topic, though the recent update improved the situation somewhat. This series stays more unstable than 11.2 by a significant factor, though.
  Weighed into the discussion of doing an out-of-plan Firefox update on Android because of a high-visibility crash on Jelly Bean.
  Kept track of the B2G crash reporting story in Bugzilla, GitHub, email and IRC discussions.
  Moved my components report over to using data from the database, now only the device reports is still based on CSVs.
  As usual, watched new/rising crashes, caring that bugs are filed where needed.
• German L10n:
  Reviewed / commented on Thunderbird 16 L10n.
  Updated ChatZilla, core and SeaMonkey L10n to recent trunk changes.
• Themes:
  Finished up work on 2.11 versions of EarlyBlue and LCARStrek, and uploaded those to AMO.
• Various Discussions/Topics:
  Mailcompose recycling crashes, localizing B2G, social API and trains, build system changes and comm-central, etc.

It's a rare day that I start my work day late and see the reason for that waiting on xkcd!
I'm still in awe how such a complex mechanism works so perfectly on the first try, esp. as I know how easy you can get things right - in the software business I think everyone is aware how hard it is to stay completely free of bugs. In my work with crash analysis, I see daily how far off that we are. All that makes me even more aware of what a feat it is to be successful with a landing like MSL/Curiosity made early today. After all, there's no second try, this needed to go right on the first shot. And it did. Awesome.