On Fri, Sep 4, 2009 at 8:52 AM, Stéphane Ducasse <stephane.ducasse@inria.fr>wrote:
Hi all
I suggest the following: we go over the bug tracker and move to 1.1 all the issues that are not showstopper and we declare pharo 1.0 done and we open pharo 1.1 alpha
Does it make sense to you? Stef
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
I know I'm still very much a n00b here, but I'll add my $0.02 anyway. Whenever I want to try something new, one of the first things I always do is to locate the test suite, run all the tests, and make sure everything is green. Right now I see that in the core beta we have 32 failures and 2 errors, and to me it does not feel like it should be a huge job to fix those before we declare a new version. I would be interested to hear if there is any good reason not to have that as a goal, and of course I would be prepared to help out if anybody agrees with my idea. -- Cheers, Peter