GemStone/S 64 126.96.36.199 was released August 28, 2012. This release fixes a number of bugs and we recommend all 3.x customers use this release. Be sure to review the release notes and install guides for this release.
GemStone 188.8.131.52 ships with GLASS 1.0-beta.8.7.2 pre-installed in
$GEMSTONE/bin/extent0.seaside.dbf, but there are a few minor issues that show up as test failures. GLASS 1.0-beta.8.7.3 has been released to address those issues.
You should update to GLASS 1.0-.8.7.3 when you start using GemStone 184.108.40.206.
A One-Click GemTools 1.0-beta.8.7 for GemStone 220.127.116.11 can be obtained from the seaside.gemstone.com downloads page or you can download GemTools 1.0-beta.8.7 for Gemstone/S 18.104.22.168 all platforms directly.
You can build a custom GemTools image by following these steps on the glass db wiki.
Seaside 22.214.171.124 should be used with GemStone/S 3.1.x. There are a few critical bug fixes included in that version.
You can download the binaries from ftp://ftp.gemstone.com/pub/GemStone64/126.96.36.199, use the installGemStone.sh script to download and install GemStone/S on your machine (highly recommended), or visit seaside.gemstone.com downloads page.
To use the installGemStone.sh script, your supply the GemStone version number as an argument to the script. The following downloads and installs the GemStone/S 188.8.131.52 release:
If you are upgrading from GemStone/S 2.x, then be sure to read my post on GemStone/S 3.1.0 first.
Let’s say that you’ve got Seaside 184.108.40.206 installed in your GemStone/S 3.1.0 repository. According to the upgrade instructions you will need to define the BootstrapApplicationLoadSpecs for your application. For Seaside 220.127.116.11, that means you’ll run the following topaz script BEFORE running the upgradeSeasideImage.sh script:
The important bits are that you are specifying GLASS 1.0-beta.8.7.3 and specifying the <path to seaside cache repository>. The seaside cache repository is a directory on your machine where you’ve stashed all of the mcz files needed to reload Seaside 18.104.22.168 into your upgraded repository. You can use the following script to create the seaside cache repository:
Finally, as noted in Issue 354, you need to reload the ConfigurationOfGLASS and ConfgurationOfSeaside30: