I think that somebody (probably not the fuel team which is full right now) should use a jSON or other formats to externatlise data out of fuel and this version should be use for old mgration.
The point of evolution is important because we should be able to load old code in the future. Now let us make sure that fuel is really working well. On Oct 10, 2011, at 11:25 PM, Mariano Martinez Peck wrote: > > > On Mon, Oct 10, 2011 at 11:19 PM, Schwab,Wilhelm K <[email protected]> > wrote: > True, but what about reading data from five years ago? > > Well, can you load your 5-year-old code out of the box? No. You will > probably need to update its code. The same here. > You can always take the same Fuel version and updated (without changing the > format) to work in a new Pharo image. Just as you do with your own code. > As an example, the last stable version 1.6 of Fuel works if Pharo 1.2, 1.3 > and 1.4. I think it is good enough. > > Cheers > > > I have ten year old Dolphin STB that I can still load. > > > > ________________________________________ > From: [email protected] > [[email protected]] On Behalf Of Igor Stasenko > [[email protected]] > Sent: Monday, October 10, 2011 4:59 PM > To: [email protected] > Subject: Re: [Pharo-project] When will Fuel file format stabilize? > > I concur with Mariano. > In production images, you want probably stick with concrete > verision(s) of frameworks you using and don't > follow the bleeding edge. Because if you do, then you spending time on > coping up with latest and greatest > versions of these frameworks instead of spending time on developing > your project :) > > -- > Best regards, > Igor Stasenko. > > > > > > -- > Mariano > http://marianopeck.wordpress.com >
