On 2013-09-02, at 11:07, Stéphane Ducasse <[email protected]> wrote:
> what we could do is to not deprecate now the methods? > Then we can deprecate them when we release 3.0 I would say the exact opposite, deprecate methods as early as possible If I deprecate a method now, - it is deprecated in the current dev version 3.0 dev - it is deprecated in the next release 3.0 stable - it is removed in the next dev version 4.0 dev so the current behavior is correct. For these issues apply the following strategy: - the latest stable version should load in 2.0 (1.4 is dead) - the latest dev version should most probably work in 3.0 So in this case, OSProcess could be easily updated to use 'Smalltalk os' since that exists already in 2.0, and nobody should even care developing or backporting software for 2.0.
signature.asc
Description: Message signed with OpenPGP using GPGMail
