> On 16 Jan 2016, at 11:59, Thierry Goubier <thierry.goub...@gmail.com> wrote: > > Le 16/01/2016 11:39, Esteban Lorenzano a écrit : >> >>> On 16 Jan 2016, at 10:45, Eliot Miranda <eliot.mira...@gmail.com> >>> wrote: >>> >>> >>> Hi Thierry, >>> >>> up until a few hours ago the latest VM sources were indeed broken >>> by work I was doing on 64 bits. My sources are AFAIA now correct >>> and I suppose you're waiting on Esteban doing a merge. But I'm >>> responding since there seems to be a process error here. >> >> is still broken :) >> >>> >>> I need the freedom to break the VM, otherwise I can only extend it >>> with difficulty. This assumes that there are currently servers >>> that build and test the VM, and implies that we maintain the notion >>> of the most recent good VM that has passed all the tests, and that >>> this is the "latest" VM everyone is using. >>> >>> If there isn't this distinction then every time I extend the VM and >>> make inevitable mistakes I affect users. That's clearly not >>> sensible. >> >> yes of course, what we have is two versions of the VM: >> >> - “latest" build is a build with latest sources… this might be >> broken. People willing to help us find bugs should use this. - >> “stable” build is the VM after it passed all tests… and that’s what >> people willing some stability should use :) >> >> what actually is happening now is that there is a lot of people >> helping in the migration of spur (something I thank, a lot) and then >> they use latest vm version… who is usually very stable (but not >> always, as is the case). > > I think the issue was that the latest vm has been very stable and that it > suddenly broke was a bit unexpected. At the same time, in the pre-spur days, > the stable was a very old build.
yes, true. Now latest spur stable is from 14/01 so… :P Esteban > > Thierry > >> cheers, Esteban >> >> >>> >>> _,,,^..^,,,_ (phone) >>> >>>> On Jan 16, 2016, at 1:21 AM, Thierry Goubier >>>> <thierry.goub...@gmail.com> wrote: >>>> >>>> Hi Guys, >>>> >>>> has something changed in string handling? I'm unable to get the >>>> latest Pharo to read files containing utf8 data. >>>> >>>> I tracked it down to a primitive (at:put:) in WideString and to >>>> the latest vm for Pharo 5, so, maybe there is something wrong in >>>> the latest vm. >>>> >>>> Thierry
