I wonder.... If the March/April integrations don't break any existing API, and the new debugger runs in parallel with the old one, then maybe that might be a 2.x release, and move to 3.0 only when PackageInfo and the old debugger are ripped out. (of course all dependent on additional load and human resource availability)

cheers -ben

Camille Teruel wrote:
Hello everyone,

Since a picture worth a thousand words, here is a summary of the next actions for Pharo 3:



Note that some tasks in "Later" may be integrated before July. Here "Later" also stands for "Not planned yet".

Camille Teruel





Reply via email to