[Seaside-dev] 3.0.3.2 or 3.0.4

[Philippe Marschall]

2011/2/8 Dale Henrichs <dhenrich at vmware.com>:
> I've done just about as much as I need to do in the Seaside3.0 port to
> GemStone3.0 so I'm ready to release 3.0.3.1.
>
> The next round of work that I'd like to do is make a pass through Magritte2
> and Pier2 picking up the latest versions of mcz files and start propagating
> symbolic versions through the Seaside/Magritte/Pier configuration ecosystem
> .... there are several places where symbolic versions can be used to
> improved the configurations that depend upon ConfigurationOfSeaside30.
>
> At a minimum I'd like to incorporate symbolic versions into Seaside for the
> handful of projects that Seaside3.0 depends upon. To that I'd need to crank
> out a new version and it would make sense to use version 3.0.3.2...if that
> was all I did.
>
> On the other hand, if 3.0.4 is ready to go out the door, I could update to
> the latest packages, port to GemStone and test on Squeak in addition to the
> symbolic version work and then of course use 3.0.4.
>
>
> So what do you guys think? Is 3.0.4 ready to rumba?

I'm not sure about the fix for Issue 640 (Seaside-Core-as.694,
Seaside-Core-as.695). I'd like to discuss that first with Lukas.

Cheers
Philippe