no stress guys. take the time and give time. there are plenty of other stuffs to do and at the end we can revert so this is quite cool The risk is low. This is not like: ok fix the %^&*( code management system because there no backup. So we should be nice and welcoming the energy that fernando is putting to improve the system. if at the end the results is not at the right level: I take 2 hours and fix everything but we should welcome hiccups in progress and let people put their energy on the table without having to do right perfect the first time.
Stef On Apr 28, 2011, at 9:51 PM, Alain Plantec wrote: > Le 28/04/2011 21:21, Marcus Denker a écrit : >> Core >> Failing Tests: NONE >> Open Issues: 23 >> http://code.google.com/p/pharo/issues/list?can=2&q=milestone=1.3 >> Related to Transcript: 8 >> >> Full >> Failing Tests: 37. Related to Nile: 30. >> https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.3/lastCompletedBuild/testReport/ >> Open Issues: 9. >> http://code.google.com/p/pharo/issues/list?can=2&q=Milestone%3D1.3-DevImage >> >> Next most important Step: >> -> fix Transcript. > what about revert the Transcript and push the new one again in 1.4 ? > Cheers > Alain > >> -- >> Marcus Denker -- http://www.marcusdenker.de >> INRIA Lille -- Nord Europe. Team RMoD. >> >> >> > >
