+1 On Jan 15, 2010, at 22:55 , Michael Roberts wrote:
> i would prefer we fix them as soon as possible. Look at the effort at > the end of 1.0. It can be really sad to try and fix all the tests at > once. Having a green baseline is much easier to manage. Even if we > can't fix the bugs immediately, we should at least discuss them and > comment them on the tracker. Then at least we can easily discuss what > code has just gone into the image. Otherwise it is somewhat of an > archeology exercice going through 100s of old updates. this will of > course be easier with the continuous integration work. > > Now of course, some bugs are *really* hard. e.g decompiler bugs. > Debugger bugs. These would be great to attack with sessions & > sprints. > > cheers, > Mike > > On Fri, Jan 15, 2010 at 9:48 PM, Stéphane Ducasse > <[email protected]> wrote: >> Hi guys >> >> may be I'm wrong but I have the impression that fixing tests as soon as they >> are broken >> in the Unstable branch could be better. Now doing that may stall our energy. >> So what do you think? >> May be an alternate process is to make progress and to do green test session >> from time to time. >> >> Stef >> _______________________________________________ >> Pharo-project mailing list >> [email protected] >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
