>
>
>> Christophe.
>>
>> [1] https://pharo.fogbugz.com/default.asp?10801
>
> Ouch. Does not bode too well for backporting that to Pharo 2.0.
>
> I'm feeling a bit down. It's either enduring bugs in 2.0 for a year or so or
> fighting every few days with 3.0 and knowing that anyway it's not production
> ready. I had to cope with 1.4 not being able to handle utf8 in the same way.
Thierry what we can do is the following:
have a look at the fix of nicolas and we can try to add to th 2.0 batch
but we should pay attention
not to introduce other bugs (because I'm afraid it will).
BTW 30 is not that instable.
> The window for my next serious developpement with Pharo is around 2014, so I
> guess I could just sit and wait.
>
> By the way, why the change in MonticelloFileTree-Core-ChristopheDemarey.97
> breaks Pharo 2.0 ?
