I agree with this. As long as Deprecated30 is nicely loadable separately, I do not see a problem with the migration.
Doru On Thu, May 29, 2014 at 4:55 PM, Marcus Denker <[email protected]> wrote: > > On 29 May 2014, at 16:52, Marcus Denker <[email protected]> wrote: > > > > > On 29 May 2014, at 16:44, stepharo <[email protected]> wrote: > > > >> I'm not convinced that remove Deprecated30 now is the best move because > not having it now may not help migration. > >> I would understand that we unload Deprecated20 > > > > We originally did it like this… but Deprecated20 was so large that we > could not keep it around, as the code > > we where cleaning was used by the deprecated, leading to a huge mess. > > > > We back than decided to unload the deprecated package at the beginning > of the development phase. > > > > So for Pharo4 we do exactly what we did for Pharo3. > > Marcus > -- www.tudorgirba.com "Every thing has its own flow"
