[Setools] Upgrading to Gjallar v0.2

Ron Teitelbaum Ron at USMedRec.com
Wed Sep 6 12:57:58 UTC 2006


Göran,

Take care of yourself, hope you feel better soon,

Ron 

> -----Original Message-----
> From: setools-bounces at lists.squeakfoundation.org [mailto:setools-
> bounces at lists.squeakfoundation.org] On Behalf Of goran at krampe.se
> Sent: Tuesday, September 05, 2006 3:39 PM
> To: Software Engineering Tools for Squeak
> Subject: Re: [Setools] Upgrading to Gjallar v0.2
> 
> Hi!
> 
> "Semmi Kozod" <rebmekop at gmail.com> wrote:
> > Hi Göran!
> >
> > You mentioned that 0.2 version is coming out soon.
> 
> Yeah, but I am semi sick right now so little energy when evening comes.
> And busy at work.
> I will try to wrap it up tomorrow though.
> 
> > I have loaded Q2v0.2-makl.176 into the image,
> > then Q2Model recreateDatabase,
> 
> Which will nuke *all*, initialize, load sample data.
> 
> > then Q2Win32InstallerBuilder prepareServer.
> 
> Which fires up all services (Seaside, Scheduler yaddayadda).
> 
> > It seems to work. I am clicking around. It feels a bit faster than the
> v0.1.
> 
> Might be a bit faster, not sure. We haven't done any serious performance
> tweaking yet. Readstrategy might be worth looking at. And also - right
> now all Seaside components are initialized on login - which explains why
> it takes a while to get in. We could do it when people click around in
> the left area on demand instead.
> 
> > The question: Is this a proper way to upgrade?
> 
> Well, almost. :) We have also upgraded other packages, I will try to
> list all used versions when doing the 0.2 release, and there is also a
> Changeset we maintain with "various fixes" that should be installed.
> 
> I am right now trying to prepare a semi auto loadscript that builds the
> dev image from a vanilla 3.8 image - which makes it easier for anyone
> that wants to "build from scratch".
> 
> There have been quite a few model changes and also a Magma change that
> makes it hard to migrate an old db. BUT... with 0.2 we have a working
> txn engine - we have actually streamed out all txns, wiped the db and
> then rebuilt it by applying all those txns from the file.
> 
> This is actually a great way to migrate old dbs - the Txn classes tend
> to not change that much. Or at least they will not, when they have
> matured a bit.
> 
> > thanks : balazs
> 
> Thanks for being on the bleeding edge! :) Feel free to ask more.
> 
> regards, Göran
> _______________________________________________
> Setools mailing list
> Setools at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/mailman/listinfo/setools




More information about the Setools mailing list