>>>>
>>>>
>
> No. Just admit that you have productions 1.4 (and maybe 1.3) hanging around,
> that 2.0 is the main development platform for Pharo users, 3.0 is where you
> make interesting stuff.
Yes we admit it and then?
We are concerned to help people.
Did you run the rules generated from 1.4-2.0 activity because we are
creating to help people migrating.
We are fthinking about having better support to automatically migrate
code based on changes (but for that we need manpower).
> And that Pharo users are at least one version behind you, and that they would
> like a bit of smoothness in the way it evolves... 3.0 gives directions; but a
> bit of backport to help with the transition would be, what, just friendly to
> your users.
This is what we are doing.
> For example, for things I am aware of:
> - backport ensureDelete to 2.0
> - backport the replacement of Keymapping on:do:
Open bug entries and propose some code.
> You have 2.0 users who have things to say and who are able to correct things
> as well; don't belittle them by saying "All software development should be
> done on 3.0" [Camillo Bruni].
Give us any ideas how to help you and we will. This is why I propose to even
undeprecate certain key features if it helps providing more stability from the
users
side. I understand that not everybody is working in 3.0.
Stef
>
> Thierry
> --
> Thierry Goubier
> CEA list
> Laboratoire des Fondations des Systèmes Temps Réel Embarqués
> 91191 Gif sur Yvette Cedex
> France
> Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95
>
