Le 22/07/2011 10:58, Stéphane Ducasse a écrit :
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
where?
in the version tool of the class browser
- the revert just does not work
do you have a scenario
Clic the button 'version' in the class browser.
May be the rate of release could be slow down to get properly working Image, no ?
Not really. When you pay a person for 3 months of work you cannot ask him to work for a year slowler. We payed benjamin for a couple of months and after we can just be happy that he is doing post actions especially when the semester will restart it will be more difficult.
My remarks were about release not the written code or added feature.
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.
Which patch? Where is the bug entry?
In bugs tracker, search for closed issue with keyword Time Profile
On which image? breaking where?
See my first email in this thread. I double check, the inheritence is broken from the Browser. Scenario: clic the inhéritence button. I will check with latest 1.3 with up to date update before adding entry in the bugs tracker. Now I have to finish some other works first. Hilaire