Hi Sean.
I’ve added the necessary changes to Fuel so that 1.9.4 now cleanly loads (with
all tests green) in Pharo 3 and Squeak 4.5.
The build matrix on the CI has been updated to account for versions 1.9.3 and
1.9.4 (across all image versions) and the development build now again only
builds for Pharo 4.
So you can now safely do
Gofer it
url: 'http://smalltalkhub.com/mc/Pharo/Fuel/main';
package: 'ConfigurationOfFuel';
load.
((Smalltalk at: #ConfigurationOfFuel) project version: ‘1.9.4')
load.
in any image version prior to the latest, and in the latest of course (so in
30, 40, Squeak4.5, Squeak4.6).
I hope this makes image migrations a bit easier. Please let us know if you have
more suggestions (as I already said, the version problem is on our list).
Cheers,
Max
> Begin forwarded message:
>
> Date: 3 Mar 2015 18:03:08 CET
> From: "Sean P. DeNigris" <[email protected]>
> To: [email protected]
> Subject: Re: [Pharo-dev] Upgrading Fuel Data
> Reply-To: Pharo Development List <[email protected]>
>
> Sean P. DeNigris wrote
>> To a newer user, this could be a confidence-shaking deal breaker.
>
> Workaround:
> 1. Revert Fuel package to v. 798 i.e. just before version bump
> 2. Materialize data
> 3. Reload original Fuel package (currently v. 804)
>
> Suggestions:
> 1. unless/until we have a Fuel migration tool, at minimum, any Fuel version
> integrated into latest Pharo must be loadable in the previous Pharo version.
> E.g. if Fuel 1.9.4 was loadable in Pharo 3.0, migration would be a bit
> awkward, but doable.
> 2. Maybe more guidance in the default error behavior would help e.g. put up
> text suggesting to either a) temporarily downgrade Fuel to whatever version
> on first materialization, or b) re-serialize in the image where the data was
> serialized after upgrading Fuel
>
>
>
> -----
> Cheers,
> Sean
> --
> View this message in context:
> http://forum.world.st/Upgrading-Fuel-Data-tp4809243p4809265.html
> Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
>
