Moved
Awhile back, we made a slight organizational change. Alice Nodelman, Mikeal Rogers, Chris Cooper and myself made a lateral shift to join forces with John O’Duinn, Rob Helmer, Ben Hearsum, Nick Thomas and Chris Cooper on the Build & Release team to create a larger, many-limbed crime-fighting robot. (Astute readers will note that Coop is actually two people) The reason for this was simple: Build & Release uses the same tools we’ve been using to drive the automation systems behind Talos, JS Testing and the Unittest machines. I think we’ve settled on the name of “Release Engineering” to describe this new beast and John O’Duinn has created some new Bugzilla components to reflect this.
What does this mean to you, the developer/tester/user? If you find a bug in one of the automated systems, you should now file that under “Mozilla.org:Release Engineering” in Bugzilla. I’ll still be monitoring Core:Testing but that should be used predominantly for Mozilla-related test harnesses and tools. We’re currently in the process of triaging Build & Release bugs and relevant bugs under Core:Testing and hope to have them re-assigned and re-bucketed within a week or two.
In other moving-related news, I’ve managed to reposition myself “closer to Greenland” as some have quipped. This shouldn’t really affect my availability for those of you in the West as I’ve shifted my hours up to compensate – this just means I get to sleep in a little more. What has been an issue is my ongoing struggle with Aliant.net to get my internet up to the speeds I’m actually paying for. They have a few more days to get this fixed and then I’m going to open up the bidding.
To the shamrock-wearers, happy St. Paddies day!
