WebVelocity 1.0 is coming soon. We're in a code freeze right now (the feature freeze was a couple of months ago) and we're rapidly approaching our definition of a release candidate.

Two things we intend to do immediately upon releasing WV 1.0 is to upgrade from VisualWorks 7.6 to VisualWorks 7.7 as our base. There have been numerous improvements to Store that we desperately want to pick up, as well as general improvements to the product all-round.

The second thing we intend to do is upgrade from Seaside 2.8 to Seaside 2.9. Since the code freeze has been working reasonably well, I thought I'd take a break from doing example apps and start doing this port now.

Huge props to the Seaside development team - the testing framework they've put together makes this process very measurable! This afternoon I imported Seaside-Platform and Seaside-Tests-Platform and used it to start building Seaside-VisualWorks-Platform. I'm down to 8 failures and 8 errors of the 165 tests in this suite.

Implementing a port of some framework is rarely fun, but a lot of the guess work has been taken out of porting Seaside now. It's sometimes fun and often a delight - except when you hit some of the more hairy parts which require some deep delving.

I'm publishing the work under two bundles - Seaside and Seaside-Testing. They are the 2.9a3 branch and it includes the Monticello importer code I'm using too. This is not so much a community effort at this point, as Cincom needs to be able to support the code and it's really in its embryonic stages right now. I intend to push some of the platform support code back in to the 7.7 base if I can too.