The only configuration I changed was ConfigurationOfGlorpDBX, it was trivial, just to make it load. I added spec for: #'pharo2.x' version: '2.5'. to ConfigurationOfGlorpDBX >> stable: Some tests failed, but AFAIR, they also failed on 1.4.
Other changes include fixing Seaside's WAImageStatus, which was also trivial but has been broken for ages. Not sure how to push these changes, especially because these are only for Pharo2.0. On 7 April 2013 11:47, Esteban Lorenzano <[email protected]> wrote: > this really cool, thanks! > > btw... if you needed to update configurations... could you commit the new > configurations to the repository for Pharo2.0? > > thanks, > Esteban > > On Apr 7, 2013, at 8:43 AM, Milan Mimica <[email protected]> wrote: > > On 27 March 2013 15:24, Esteban Lorenzano <[email protected]> wrote: > >> Hi, >> >> Here in Pharo headquarters we are shock that there are just 10 new bugs >> reported for 2.0 after the release... >> So... I wonder... is that because we made a really cool release, or just >> because nobody is using it? >> > > I know you must be starving for feedback on Pharo 2.0, so here is mine. > > I ported my app to it, from Pharo 1.4. The app uses Glorp, Seaside, RFB > and HPDF, so it took me an afternoon. > The overall impression is great. Unlike 1.4, it didn't crash a single > time. Another great thing is that you didn't make that many backward > incompatible changes as I though you would. Of course, I had to patch > almost all of the above (their dependencies include FFI, OpenDBX etc.) and > rewrite some little bits of my code, but it was worth it. The new FS > classes are must better. > From user's point of view there is no much difference to 1.4, which is a > good thing. I know you revamped things internally. > > Keep the good work, and I hope I will be able to provide you with feedback > from real production environment soon. > > > -- > Milan Mimica > http://sparklet.sf.net > > > -- Milan Mimica http://sparklet.sf.net
