[Pharo-project] Need help with 1.3 Full Image

Stéphane Ducasse stephane.ducasse at inria.fr
Fri May 13 19:39:56 CEST 2011

We will soon integrate RBEngine, AST, into core so you will have less to maintain.
Now for me, what is important is not the number of bugs but the ratio of new things/bugs
and I think that it is pretty low when we take into account all the changes and improvements
we did. Having a better textEditor is important.
Now this is ok that you do not have time, we understand that too, I know what is to 
move, get a new job and be credible (I did that twice over the last 5 years) 
but then after we suffer that you start to complain after the release when we give 3 months of 
RC candidates. 


On May 13, 2011, at 6:41 PM, Lukas Renggli wrote:

> Hi Stef,
>> uh? what are these bugs?
> From the top of my head these are all bugs that appeared in the past
> weeks and that were not present in Pharo 1.1:
> - temps and method selector changes that disappear and that are not
> logged in the changes file
> - text formatting that vanishes from larger texts
> - mouse selection that is broken
> - various OB bugs, such as broken smart chars, scroll bar, tests, text
> search, ...
>> I'm really surprised. I'm also surprised that you say that when you did not
>> even tried to port your tools to 1.2 during the release candidate phase and that people
>> tried and failed and you started to port your tool when 1.2 was released.
>> You were undermining our process sadly.
> I was moving to a different place, starting with a new job, and
> learning new things.
> I don't have the energy and interest to constantly run after the
> latest releases. I want to use something stable to work with in the
> little spare time I have, and not be constantly disturbed by new
> problems that show up because something subtle changed. For me Pharo
> 1.2.x will be the last version until something really compelling shows
> up ...
> Lukas
> -- 
> Lukas Renggli
> www.lukas-renggli.ch

More information about the Pharo-project mailing list