[Seaside] The best combination of stuff for SeaSide?

[Stephen Pair]

Yoshiki.Ohshima at acm.org wrote:

>  Stephen,
>
>  Thank you for the suggestion.  I'm not going to need any fancy
>features for short term, and try to minimize the change to Commanche
>or Seaside as little as possible (although I'm anticipating that
>Japanization will require some change.)  The version difference
>shouldn't matter too much, I think.  If you think that 6.1 is
>"beta"-enough, which it seems you do, I think I can go ahead with 6.1
>and applying patches from you later on.  A problem would be to distill
>the "good" patches from the flood of emails...
>

I'll certainly post an email when I put up new builds of 6.1 beta.  But, 
you can also monitor the build numbers to see if there are new builds 
available.  To check the build number, you can look at the "notes" link 
on the download website (http://squeaklab.org/comanche).  To see what 
build is in your image, use:

    KomHttpServerInfo default buildNumber

The same applies for all of the various Comanche packages (KomServices, 
DynamicBindings, etc).  The info class is always named like: 
<PackageName>Info.

After a few weeks (during which time I hope any major bugs are found and 
fixed), I'll mark 6.1 stable, which means that there will be no further 
builds of 6.1 (or any of its pre-requisite packages). Any further 
critical bugfixes will go into 6.1.1.  Those bugfixes will also go into 
6.2 alpha along with new features.

Also, when loading any of the Comanche packages, keep a Transcript 
open...there is useful information that gets printed in the 
transcript...the most useful is the report of Sunit tests being run, and 
their success/failure status.  Comanche doesn't have many tests at the 
moment, but I'll be adding them (especially as bugs get reported and fixed).

- Stephen