[Seaside-dev] [Seaside] Build Process
dhenrich at vmware.com
Sat Mar 5 21:01:13 UTC 2011
the commits are suspended because the final release image/changes comes from the Hudson build, but since hudson doesn't use Metacello, the two can easily get out of synch.
If there was a hudson build dedicated to building from the Seaside3.0 metacallo configuration and if the image/changes for the release came from that build, then suspending commits wouldn't be necessary ...
You picked a doozy of a build to look at tho:) Not only did I run into a series of bugs while just loading and testing for Pharo, but I had a number of GemStone-related issues pop up during the porting of the changes to GemStone, not to mention a number of non-Seaside-related issues to boot. In the past, there were few update/test errors and the port to GemStone was quick.
On Mar 5, 2011, at 8:34 AM, Avi Shefi wrote:
Having watched the build process for the first time, it looks like there are some complicated steps involved.
I have read the MakeRelease document on the Wiki, and I wondered if there's room for further improvements/automation ?
If there's one issue that particularly captured my attention, it was the fact that we had to stop further commits to the repository during the build.
I'd love to hear your thought about this.
More information about the seaside-dev