You are currently browsing the category archive for the 'Releases' category.
On Tuesday we announced the release of GemStone/S 64 version 2.3.1. This release is primarily a bugfix release for our commercial customers. The critical bugifixes are not likely to affect anyone using Seaside. For complete details please refer to the Release Notes.
The release can be obtained from the GLASS downloads page.
New installations should always use the latest available product release, but for this particular release unless you are suffering from one of the bugs that has been fixed you can safely defer the upgrade.
2.3.1 ships with GLASS.230-dkh.176 so you should update to GLASS.230-dkh.177.
We have no plans to release a new version of the appliance. 1.0beta11 is still the most recent version.
——
[1] Photo by jasonpearce via Flickr (Creative Commons).
Last Friday we announced the release of GemStone/S 64 version 2.3. We’ll be publishing a new version of the appliance (1.0 beta11) now [updated: 10/11/2008]in a week or so.
From a GLASS perspective, there are a handful of new features in the 2.3 release:
- Support for full Unicode character range with introduction of QuadByteString and MultiByteString classes
- Primitive support for UTF8 encoding (100x faster than Smalltalk-based algorithm).
- Primitive support for HTML encoding.
- Thread local support for GsProcess and continuations. Thread locals are being used in Seaside2.9.
- Improved ProfMonitor output code moved from GLASS-only to base image.
For a full description of the new product features and bugfixes, check out the Release Notes.
Also note that there are new versions of the System Administration Guide and Topaz manual for 2.3.
GLASS.230-dkh.164
Between the last Beta Update (GLASS.230-dkh.162) and the 2.3 product release, I managed to slip in a couple of bugfixes for Pier and FastCGI. As I mentioned earlier, Pier 1.0.17 is installed as part of the Seaside release in 2.3.
Download
You can find 2.3 downloads for Mac and Linux on the Glass Downloads page.
Installation
Follow the instructions in the Install Guide, or follow James Foster’s instructions and/or screencast. James’ instructions are aimed at installing 2.3 on Slicehost, but his instructions are useful for any *NIX install.
Upgrading
If you have been using 2.2.5, you will want to upgrade your repository from 2.2.5 to 2.3. Start by following instructions in the Install Guide for “Upgrading from previous GemStone/S 64 Bit 2.x versions” and after those steps have completed without error, run
$GEMSTONE/seaside/bin/upgradeSeasideImage [...]
using the same arguments you used with the upgradeImage script. This script ensures the SessionMethods are enabled, updates the UTF8Encoding package to to Utf8Encoding.230-dkh.21 and recompiles all methods that are managed under Monticello. Utf8Encoding.230-dkh.21 is the required for correct UTF8 encoding of DoubleBytesStrings and instances of the new class QuadByteString.
Assuming that you were running with GLASS-dkh.122, with the inclusion of the new UTF8 package, you will be running with the same code as GLASS.230-dkh.162, so after the upgrade is complete you will want to load GLASS.230-dkh.164 so that you are using the latest code. If you are using a custom-built repository, then you will want to update your build scripts to use Utf8Encoding.230-dkh.21 for future builds.
I’ve run several successful tests using this upgrade script on several different repositories, one of which dates back to 1.0beta6 (I’ve been continuously upgrading it since last February), but I will be interested in any issues that folks may run into in upgrading their 2.2.x Seaside repositories. If you have a Maintenance agreement with GemStone, please submit any bug reports through the Technical Support site, otherwise submit mail to the Beta Mailing list (subscription required) and we’ll help resolve any issues you may run into.
We just announced the release of GemStone/S 64 version 2.2.5.1.
2.2.5.1 includes a Seaside extent based on GLASS-dkh.114. For our Seaside users we fixed a bug related to remote breakpoints, so that with 2.2.5.1, you can set/debug/resume remote breakpoints.
As I mentioned for 2.2.5, most Seaside users should wait for the 2.3 beta appliance. 2.2.5.1 was created primarily for those Seaside users that need a production release for development as well as deployment.
Yesterday we announced the release of GemStone/S 64 version 2.2.5. Check out the Release Notes for more information.
From a GLASS perspective we fixed only a hand full of bugs. The 2.2.5 release primarily contains features and bugfixes for a commercial customer.
For GLASS users, I recommend that you wait for the 2.3 beta that is scheduled to be available at the end of this week.
Yesterday we announced the release of GemStone/S 64 version 2.2.4. Check out the Release Notes for more information.
From a GLASS perspective, there were a handful of changes made to the base product:
- Curly brace Array constructors added to the Smalltalk compiler.
- Support for Squeak-style Pragmas.
- Notification mechanism for abortTransaction, beginTransaction, commitTransaction, and transactionMode:. (see the class SessionMethodTransactionBoundaryPolicy).
- Notification mechanism for sessionStart (see the class SystemLoginNotification).
You need the changes in version 2.2.4 in order to use the GLASS tools. As of today, you can load the Monticello package GLASS-dkh.57.mcz into GemStone/S from the GLASS repository (you will need GemStone-dkh.234.mcz loaded into your Squeak image as well).
In addition to the base support for Monticello and Seaside, GLASS-dkh.57.mcz includes several packages from the SeasideExamples, Scriptaculous, SeasideAsync, Magritte, and Pier. All of the unit tests are passing for the packages. You can look at the version history for GLASS-dkh.57.mcz to get a blow by blow account of the changes.
In the last week before shipping 2.2.4, we found a bug that affects doing a proceed from a halt or breakpoint when debugging Seaside applications. In order to fix the bug, we had to make changes to the C executables. Since 2.2.4 is being released to customers for production applications, we didn’t want to delay 2.2.4, so the bugfix wasn’t included.
After the 2.2.4 release, we did a beta build for version 2.2.5 and included the bugfix. The new version of the appliance (which is in the final phases of production) is being built with the 2.2.5 beta. I recommend that everyone use the 2.2.5 beta for Seaside development.
