We should be restrained at the start of Pharo 4 development too because we firstly need to improve modularization of the system. It's common that at the start of the development cycle a huge amount of various modifications is integrated and often with only little regards on modularization. Then to improve the Pharo in this frontline is very hard and ungrateful task. At the start of the new release we firstly need to change our system and integration tools to take this into account...
Cheers, -- Pavel 2014/1/24 Marcus Denker <marcus.den...@inria.fr> > > On 24 Jan 2014, at 13:11, Sean P. DeNigris <s...@clipperadams.com> wrote: > > > EstebanLM wrote > >> *please* stop cleaning, enhancing, and modifying the image in any way > > > > Sorry :) I got burned by Morphic in a personal project and went on a > rabid > > cleaning. In all fairness, I tagged some of those "later" :-P > > > > We really need to stop. I integrated you Morphic cleanup and now we got a > comment > on the bug tracker (from someone who wanted to work on another bug): > > “ Why do I hate it when I tried to build a new 3.0 image to improve > that slice, that the image building ends in : > > KeyNotFound: key #TasklistMorph not found in SystemDictionary > > because of my settings?” > > > WE NEED TO STOP. > > Marcus >
