For short term stability I would recommend that you change as little as is necessary.
Since you are currently running on 184.108.40.206, 220.127.116.11 is the latest version of GemStone that you should consider. 18.104.22.168 has a number of potentially critical bugfixes in it and 22.214.171.124 has new heartbleed ssl libraries. If you aren't experiencing any problems in your application then you can probably sit tight on 126.96.36.199, but I think it would be a good idea to put plans in place to move to 188.8.131.52 (or 184.108.40.206 if and when it is released when it is practical for you....
It's always a good idea to be running on the latest point release of GemStone, but it isn't always practical nor are you necessarily exposed to the bugs that have been fixed.
There are enough changes in 3.2 (at the image level and below) that it would be prudent to fully qualify your application in 3.2 before releasing into production and that is more of a mid term project.
On Fri, May 30, 2014 at 6:43 AM, Dario Trussardi <[hidden email]> wrote:
i have a Pharo1.4 with Seaside 3.0 application to port into GLASS.
Now i have a server where run Gemstone 220.127.116.11 with Seaside 3.0.
The last year it works fine.
My questions is: i can rely on this release ?
Or as minimum i need to load Gemstone 18.104.22.168 ?
If yes; i can migrate from 22.214.171.124 to 126.96.36.199 ?
Alternatively, i read about new Gemstone 3.2,
but i don't understand which Seaside version i can run on it without problem.
I have to define a valid configuration for the coming months.