With GLASS 1.0-beta.8. I am finally providing an upgrade path for GLASS.230-dkh.231, the GLASS Appliance 1.0beta11 (GLASS.230-dkh.164), and GemStone/S 64 2.3.1.


There are a number of changes that take effect with the 1.0-beta.8 release (part of the reason that the release has taken so long):

There are outstanding tasks that need to be completed before the entire 1.0-beta.8 release process is complete and you should keep an eye on the 1.0-beta.8 Release tasks for monitoring progress towards completion. Here is a list of the major milestones that are pending:

With all of that said, 1.0-beta.8 is ready to be used:

So have at it and let me know if you have problems.

1.0-beta.8 Upgrade Instructions

If you have an existing instance of GLASS including:

Upgrade your installation by following these steps:

  1. Create a GemTools client image (Steps 3 through 8 on the Getting started with GLASS page) based upon Pharo or Squeak
  2. Make a backup of your starting extent (Step 9 on the Getting started with GLASS page)
  3. Update GLASS to 1.0-beta.8 (Steps 10 and 11 on the Getting started with GLASS page)

If you have upgraded from a version earlier than 1.0-beta.0, then you are done! The upgrade for optional projects was performed as part of the GLASS update.

If you are upgrading from 1.0-beta.0 or later, then you are not quite done with the upgrade process.

Upgrade Optional Projects for 1.0-beta.0 and later

The 1.0-beta.8 GLASS configuration no longer manages all of the GLASS projects directly. Only a handful of fundamental GLASS projects are being managed. To finish the upgrade process you will need to individually upgrade the optional projects like Seaside28Seaside30 or SOAP.

For post 1.0-beta.0 upgrades, you should pick and choose from the projects and load only those projects that you are using or want in your repository.

The implication of having optional projects is that the fundamental GLASS projects and the optional projects can now be upgraded independently, so monolithic releases are no longer necessary.

The MetacelloRepository on GemSource is where the configuration for projects that are known to work in GLASS are stored:

  • ConfigurationOfGLASS
  • ConfigurationOfGofer
  • ConfigurationOfGoferProjectLoader
  • ConfigurationOfGrease
  • ConfigurationOfGsCore
  • ConfigurationOfGsFastCGI
  • ConfigurationOfGsHyper
  • ConfigurationOfGsMisc
  • ConfigurationOfGsMonticello
  • ConfigurationOfGsOB
  • ConfigurationOfGsScaffolding
  • ConfigurationOfGsSeasideTesting28
  • ConfigurationOfGsSOAP
  • ConfigurationOfGsSqueakSource
  • ConfigurationOfMagritte
  • ConfigurationOfMetacello
  • ConfigurationOfPier
  • ConfigurationOfPierAddOns
  • ConfigurationOfSeaside
  • ConfigurationOfSeaside28
  • ConfigurationOfSeaside28Examples
  • ConfigurationOfSeaside30
  • ConfigurationOfSwazoo2
  • ConfigurationOfXMLSupport

Any one of the above configurations can be loaded on top of GLASS 1.0-beta.8.

Using Gofer one can load the latest version of Magritte using the following expressions:

Gofer new
	gemsource: 'MetacelloRepository';
	package: 'ConfigurationOfMagritte';
(Smalltalk at:#ConfigurationOfMagritte) project latestVersion load.

Even though Gofer drastically reduces the complexity of the load expressions involving Monticello, there is still room for improvement when loading configurations and that’s where Gofer Project Loader comes into play.

Using Gofer Project Loader the following expression is equivalent to the previous Gofer expression:

Gofer project load: 'Magritte'.

With Gofer Project Loader you can specify a default repository (for GLASS: Gofer Project Loader is also aware of the ‘ConfigurationOf’ convention, so it isn’t necessary to type the leading ‘ConfigurationOf’.

The Gofer Project Loader expression:

Gofer project load: 'Magritte' version: ''.

loads version ‘’ from ConfigurationOfMagritte and:

Gofer project
    load: 'Magritte' 
    version: '' 
    group: 'Magritte-Seaside'.

loads the ‘Magritte-Seaside’ package (along with the dependent packages of ‘Magritte-Seaside’) from version ‘’ of ConfigurationOfMagritte.

The following Gofer expression is useful if you would like to just load the ConfigurationOfMagritte without loading the Magritte project itself:

Gofer new
	gemsource: 'MetacelloRepository';
	package: 'ConfigurationOfMagritte';

It should be obvious by now that it will be worthwhile spending some time learning about Metacello (take the Metacello Tutorial), Gofer and Gofer Project Loader. I think you will find Metacello it very useful to build a Metacello configuration to manage the packages in your own project. / CC BY-NC-ND 2.0