Given the amount of changes in Pharo it is normal stuffs get broken and some tests need to be human conducted, therefore a list of features to test before release could be used to review the needed working features. Wiki shared, the workload on this list can be easily contributed by anyone.
I just see problem in the the version tool of the browser: - the tool does not show the diff properly: no way to read what is new and old - the revert just does not work May be the rate of release could be slow down to get properly working Image, no ? Regarding the problem with the Time Profile, I see a patch from Bert, but upgrading my image just broke, so I can't test it for now. Hilaire Le 21/07/2011 21:09, Stéphane Ducasse a écrit : > this is mainly a ui concern. > > On Jul 21, 2011, at 8:58 PM, Igor Stasenko wrote: > >> On 21 July 2011 20:29, Mariano Martinez Peck <[email protected]> wrote: >>> >>> >>> On Thu, Jul 21, 2011 at 6:14 PM, Stéphane Ducasse >>> <[email protected]> wrote: >>>> >>>> it depends on your scenario and when users do not use or use the tool >>>> differently you get different feedback. >>> >>> Or even better: if noboy says anything in the last 6 months while Pharo 1.3 >>> was being developed/tested then we cannot do magic. >>> I am tired of saying that anything that YOU don't test, can be broken. >>> >> >> why "can be"? it definitely will be broken. >> >> What would be nice is to write tests for TimeProfileBrowser to prevent >> regressions. >> Any ideas? >> >> -- >> Best regards, >> Igor Stasenko AKA sig. >> > > > -- Education 0.2 -- http://blog.ofset.org/hilaire
