You are currently browsing the daily archive for October 21, 2011.
GLASS 1.0-beta.8.7 has been released. I’ve been pretty busy since the last GLASS release in March: there are almost 50 bugfixes included in this release.
GLASS 1.0-beta.8.7 has been tested against GemStone/S 2.3.1, GemStone/S 2.4.4.1 and the forthcoming GemStone/S 3.0.1 release.
I plan a series of blog posts over the next few weeks to cover some of the more interesting changes and new features included in and enabled by GLASS 1.0-beta.8.7.
GemStone/S 2.3.1 Upgrade
If you’ve downloaded the GLASS appliance, you will be running on GemStone/S 64 Version 2.3 and GLASS.230-dkh.164. The good news is that you can upgrade from GLASS.230-dkh.164 to GLASS 1.0-beta.8.7:
- Update your GemTools image to GemTools 1.0-beta.8.5.
- Update GLASS to 1.0-beta.8 which gets you to the point where Metacello is installed. This step can take awhile, so be patient.
- Update GLASS to 1.0-beta.8.7.
- Update the rest of the projects that were part of GLASS.230-dkh.164, most notably:
- Seaside 2.8.5
- Magritte 1.2.1.5
- Pier 1.2.1.6
As always don’t forget to make a backup before and after the upgrade.
GemStone/S 2.4.4.1 Upgrade
GemStone/S 2.4.4.1 and the subsequent 2.4.x releases have all shipped with GLASS 1.0-beta.8.1 pre-installed in the seaside extent ($GEMSTONE/bin/extent0.seaside.dbf). The upcoming GemStone/S 2.4.5 release will be shipped with GLASS 1.0-beta.8.7 pre-installed.
To upgrade to GLASS 1.0-beta.8.7:
- Update your GemTools image to GemTools 1.0-beta.8.5.
- Update GLASS to 1.0-beta.8.7.
- Make a backup.
—–
http://www.flickr.com/photos/mcbridejc/6165651180 / CC BY-NC-SA 2.0
GemTools 1.0-beta.8.5 has been released. With this release there have been several bugfixes:
- Issue 132 : Use System class>>#”cacheName:” to make session recognizable in vsd
- Issue 250 : order and size of args asociated with #halt changed in Gci3xErrStype64 (GemStone 3.0)
- Issue 280: GemTools login error: ”Network error – text follows”, does not follow with error message…
- Issue 291: Maintenance Gem Topaz Exit 3.0 / GemStone 3.0
as well as some tweaks to the GLASS upgrade process.
Upgrades
I always recommend that you update GemTools before upgrading GLASS, because the GLASS upgrade process is driven by code included in GemTools. When you select the Update GLASS menu item, the class OGUpgradeJadeServer (included in the GemTools distribution) is compiled on the server and is then used to control the upgrade process.
Speaking of upgrading GLASS… If you are interested in doing a GLASS upgrade from a topaz script take a look at this page on the glassdb wiki has the most up-to-date instructions.
Help
Don’t forget that when you load GemTools into Pharo and Squeak, a set of Help Browser pages are created to provide the most up-to-date information on getting started with GemStone and the GemTools image.
Pharo
Before releasing 1.0-beta.8.5, I tried loading GemTools into some of the more recent Pharo releases, like Pharo 1.3 and Pharo 1.2, but unfortunately the OmniBrowser implementation in those images is incompatible with the OmniBrowser required for GemTools. The latest version of Pharo that I found that works with GemTools is Pharo1.1.2-11422.
Squeak VM versions
While we’re on the subject, you should also be aware that in order to connect to GemStone, you must use an older version of the Squeak vms (4.2.2 or older) to avoid an FFI bug. For more details, see Issue 258.
—–
http://www.flickr.com/photos/nhankamer/5616046050 / CC BY-NC 2.0
Metacello 1.0-beta.31 has been released. The primary motivation for the release is support for GLASS 1.0-beta.8.7:
- Use Gofer 1.0.5.1 which addresses some GemStone problems.
- GemStone variant of the fix for Pharo Issue 4613: programmatic calculation of platform attributes.
and change that affects the sort order for branched Monticello packages:
In previous versions, the branch name took precedence over the version number when sorting Monticello packages. This had the effect of preventing branched Monticello packages from being loaded on top of a non-branched Monticello package which is not correct. Moving forward the version number takes precedence over the branch name and the branch name is only used to break a version number tie.
—–
[1] Photo by http://www.flickr.com/photos/ucumari/1335533357 / CC BY-NC-ND 2.0
