ok guys run the tests and send fixes :) On Jan 16, 2010, at 3:11 AM, csrabak@bol.com.br wrote:
Em 15/01/2010 19:48, Stéphane Ducasse <stephane.ducasse@inria.fr> escreveu:
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.
I think it would reduce the [apparent] speed of new functionality, but not "stall our energy" which I surmise is to have a cool but as bug free as possible Pharo Smalltalk.
So what do you think?
Doing this way, as some red tests get on the pile without resolution we can get more attention to the issues.
It's a mixture of the Toyota process with a Kanban for squashing the bugs!
May be an alternate process is to make progress and to do green test session from time to time.
Except if we could be _so_ assertive about the non importance of some of the non passing tests, I think the time to time should be as short as today!
OK, as a concession could we try to have these gates about every two weeks?
-- Cesar Rabak
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project