I think the broken build is good. It shows that the process of building releases is not stable. Not stable in this case means you don't have control over what is going on. Building releases with x.y.z version numbers forces you to have control over it to some extent. I think a main point of having the configurations is not to have to check every individiual version of every package everytime. If you don't have the control and you care about release 1.2.1 is not significantly different than 1.2.2 wouldn't have to check each version of each package every time afterwards-
I would agree that this can be considered a "no show stopper" but I would be cautious to make a habit out of it. Norbert Am 24.03.2011 um 00:40 schrieb Igor Stasenko: > Guys, i think you approach to the problem at wrong angle. > Pick any successful Pharo 1.2 build. Declare it as release. Milestone > passed. Done. > > Nobody cares that something gets wrong after, as result of ongoing > development. That the way it goes.. Something got broken, > something got repaired. > > My impression that you just stumbled over insignificant mercantile detail. > Make it perfect on next release. Lets just move on. >
