Hilaire

Yes you can load and old version and it should behave with the old behavior and��

potentially old bugs. You have the right. This is what a configuration gives you.��

Now esteban has the right to only add features and fix bugs in the maintained versions.��

And he could also consider that he does not want to help people using old versions because

he is spending a lot of time improving the new ones.

Apple, M$ and plenty of others do it this way and they have a lot more money than us.��

Stef

On Sat, Mar 25, 2017 at 7:46 PM, Hilaire <hilaire@drgeo.eu> wrote:

It is not a new project. It started with Pharo3. Then I see no reason
why I can't load the Voyage code of the time of Pharo4, with the
matching code version. It should be still there, is not the purpose of
Configuration? Or may be I misunderstand how version is working and its
purpose.

Hilaire

Le 25/03/2017 �� 18:08, Esteban Lorenzano a ��crit :
> then aside that�� one thing I do not understand is why you are develop a
> new project with an old (and not maintained anymore) Pharo version?
> Currently supported version is Pharo5, and even if Voyage is an external
> project, usually development follows Pharo stable version��
>

--
Dr. Geo
http://drgeo.eu