[Glass] Questions about upgrading from GemStone 3.6.5 to GemStone 3.7.x

[Otto Behrens]

Thanks, Steven, that helps a lot.

Otto Behrens

+27 82 809 2375
[image: FINWorks]
[image: FINWorks] <http://za.linkedin.com/in/waltherbehrens>
www.finworks.biz

Disclaimer & Confidentiality Note: This email is intended solely for the
use of the individual or entity named above as it may contain information
that is confidential and privileged. If you are not the intended recipient,
be advised that any dissemination, distribution or copying of this email is
strictly prohibited. FINWorks cannot be held liable by any person other
than the addressee in respect of any opinions, conclusions, advice or other
information contained in this email.


On Wed, Aug 26, 2026 at 1:02 AM Steven Baker <
steven.baker at gemtalksystems.com> wrote:

> Hello,
>
> > Then, to upgrade production extents, we will run the "upgradeImage"
> script. Should we run the "upgradeSeasideImage" script before loading our
> code,
>
> This is correct.
>
> > considering that loading our libraries would effectively "downgrade" the
> Seaside libraries again?
>
>
> upgradeSeasideImage doesn't install or upgrade Seaside, it just prepares
> the image to be able to load Seaside by updating some tooling (Metacello,
> Monticello, Gofer, and some GemStone/Squeak compatibility bits), and
> prepares the image so that your Seaside code can be loaded.
>
> This will make your image match the seaside extent that is shipped with
> 3.7.x, and you can load your Seaside code on top.
>
> -Steven
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gemtalksystems.com/mailman/archives/glass/attachments/20260826/c7e2ed54/attachment.htm>