http://oduinn.com ...my CyberSoapBox! Thu, 15 May 2008 08:05:38 +0000 http://backend.userland.com/rss092 en On 1.9/trunk, its important to point out that almost all of these 88 machines need to remain up, and working perfectly, in order to keep the 1.9/trunk tinderbox tree open. If one of these machines dies, we usually have to close the tree. This is because most of these machines are ... http://oduinn.com/2008/05/14/we-have-how-many-machines-dedicated-specialised-slaves-vs-pool-of-identical-slaves/ Belatedly, I'd like to welcome two new faces here in Release Engineering. Armen Zambrano Gasparnian(armenzg on irc) started last week, and he will be working trying to untangle some of our l10n infrastructure.  Lukas Blakk (lsblakk on irc) started here this week, and she will be working with Robcee on ... http://oduinn.com/2008/05/09/some-new-faces-in-releaseengineering/ While the sheer number of machines in my previous post surprised all of us, its more interesting to note that its not enough. Its simply just not enough. Even today, we're constantly under the gun, bringing new machines online as fast as possible. The 30 machines marked idle/waiting-to-mothball will all be ... http://oduinn.com/2008/05/08/we-have-how-many-machines-and-whatdy-mean-its-not-enough/ As best as I can tell, it looks like we have the following machines running on each branch: 02 machines for 1.8.0 + 29 machines for 1.8 + 88 machines for 1.9/trunk + 33 machines for moz2 ==== 152 machines in use today + 10 ref-images + 30 machines idle/waiting-to-mothball ==== 192 machines total 1) These numbers do not include any ... http://oduinn.com/2008/05/07/we-have-how-many-machines/ We used the Thunderbird2.0.0.14 release to get Rick Tessner at MozillaMessagingCo up to speed. There's a lot of Build mechanics to take in, so its not fair to add extra pressure by measuring all the wall-clock times. Rick is also working to have the existing release automation we use for Firefox ... http://oduinn.com/2008/05/04/no-wall-clock-numbers-for-thunderbird-20014/ Mozilla released Firefox2.0.0.14 on Wednesday 16-apr-2008, at 3:05pm PST. From “Dev says go” to “release is now available to public” was just over 12 days (12d 3h 20m) wall-clock time, of which Build&Release took just over 3.5 days (3d 14h 35m). 11:45 04apr: Dev says “go” for rc1 13:20 04apr: FF2.0.0.14 builds ... http://oduinn.com/2008/05/04/firefox-20014-by-the-wall-clock-numbers/ Trying to describe how our various build, unittest and talos systems connect together is tricky. The Release Engineering group spent a week all together recently, with lots of diagrams on whiteboards, just to explain it to each other. Trying to describe it *without* a whiteboard is even more tricky... and there's ... http://oduinn.com/2008/04/24/so-how-exactly-do-all-the-automated-build-and-test-systems-connect-together/ Recent blog posts by John, Asa and Matt happened as my home WinXP computer offered to "update" Safari... something I have never installed!?! Most comments on their blogs can be paraphrased as "you're only complaining because its a competing browser"... or "you're only complaining because it somehow costs Mozilla money". Thats missing ... http://oduinn.com/2008/04/17/software-update-channel-software-distribution-channel/ Mozilla released Firefox2.0.0.13 on Tuesday 25-mar-2008, at 16:30pm PST. From “Dev says go” to “release is now available to public” was 15.25 days (15d 5h 55m) wall-clock time, of which Build&Release took just over 2.33 days (2d 8h 10m). 10:35 10mar: Dev says “go” for rc1 14:50 11mar: FF2.0.0.13 builds started 16:55 11mar: ... http://oduinn.com/2008/04/12/firefox-20013-by-the-wall-clock-numbers/ Mozilla released Firefox3.0beta4 on Monday 10-mar-2008, at 17:25pm PST. From “Dev says go” to “release is now available to public” was just over 7 days (7d 6h 10m) wall-clock time, of which Build&Release took just over 3 days (3d 2h 05m). 11:15 03mar: Dev says “go” for rc1 16:10 03mar: 3.0b4rc1 builds ... http://oduinn.com/2008/04/09/firefox-30beta4-by-the-wall-clock-numbers/