<< Weekly Status Report, W19/2009 | The roads I take... | Integration eines Magento-2-Webshops mit FreeFinance und selbstgebautem Warenmanagement >>
Weekly Status Report, W20/2009
Here's a summary of SeaMonkey/Mozilla-related work I've done in week 20/2009 (May 11 - 17, 2009):
I hope we can figure out the Parallels VM network losses and the Mac VM instability cited above, as once I have figured out the L10n build stuff, the new configuration should be on par with the old and able to take over production, which will make maintenance of our build and test boxes easier and ultimately enable us to do builds with Mozilla trunk as well as move towards release automation, which again will be a huge leap forward.
All that currently needs almost my full work time although I should take care of other stuff as well, but once this all is finished, the build and release processes should be easier to take care of, so ultimately I should have more time for other things. Let's hope it actually will work out that way!
- SeaMonkey Build Machines:
I once again spent almost all my time on the build machines, trying to get things running more stable, evaluating what a Parallels server upgrade helped us, setting up the 64bit box and getting it imaged, making automatic start of buildbot on slave reboots work everywhere (though a windows slave has problems apparently caused by that), getting our improvements into buildbotcustom, and closing step 1 of that new buildbot setup.
We now have that setup produce nightlies that are put into latest-comm-1.9.1 for testing and should work identically to the still official nightlies from the old configuration.
A number of things still have to be resolved until the new configuration can move to production (sucking the old buildslave machines into the new generic pools) and beyond, for all of which I have filed bugs now: localized builds, Mac VM crashes/reboots, x86_64 build/linking problems, getting graphs up, finally getting the release harness to work. - Various Discussions:
SeaMonkey tabmail work, mozilla.org planning, Mozilla meeting times, starting thoughts on new stable security release, etc.
I hope we can figure out the Parallels VM network losses and the Mac VM instability cited above, as once I have figured out the L10n build stuff, the new configuration should be on par with the old and able to take over production, which will make maintenance of our build and test boxes easier and ultimately enable us to do builds with Mozilla trunk as well as move towards release automation, which again will be a huge leap forward.
All that currently needs almost my full work time although I should take care of other stuff as well, but once this all is finished, the build and release processes should be easier to take care of, so ultimately I should have more time for other things. Let's hope it actually will work out that way!
Entry written by KaiRo and posted on May 18th, 2009 17:48 | Tags: L10n, Mozilla, SeaMonkey, Status | no comments | TrackBack
Comments
No comments found.