May 29, 2014
2:52 p.m.
On 29 May 2014, at 16:44, stepharo <stepharo@free.fr> 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.
40005 13278 ContextPart and MethodContext merged, remaining bugs https://pharo.fogbugz.com/f/cases/13278
13282 Failing test: testGForceInria https://pharo.fogbugz.com/f/cases/13282
- Unload Deprecated30