On Fri, Sep 4, 2009 at 8:52 AM, St�phane Ducasse <span dir="ltr">&lt;<a href="mailto:stephane.ducasse@inria.fr" target="_blank">stephane.ducasse@inria.fr</a>&gt;</span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">


Hi all<br>
<br>
I suggest the following:<br>
 � � � �we go over the bug tracker and move to 1.1 all the issues that are<br>
not showstopper<br>
 � � � �and we declare pharo 1.0 done<br>
 � � � �and we open pharo 1.1 alpha<br>
<br>
Does it make sense to you?<br>
Stef<br>
<br>
_______________________________________________<br>
Pharo-project mailing list<br>
<a href="mailto:Pharo-project@lists.gforge.inria.fr" target="_blank">Pharo-project@lists.gforge.inria.fr</a><br>
<a href="http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project" target="_blank">http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project</a><br>
</blockquote></div><br>I know I&#39;m still very much a n00b here, but I&#39;ll add my $0.02 anyway. <br><br>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.<br>

<br>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.<br clear="all">
<br>-- <br>Cheers,<br>Peter<br>