> So to explain: waiting two days until making the link on the download page: > ok. We did that. Not announcing it yet. Ok, > we will announce when it's clear it's stable. But having people download an > old image without the bug-fixes by default? > No. > > We are already in Beta. Clearly marked. There is no need for a private, more > secret special beta. What is a Release Candidate meant for?
Well, I think, it is meant to be downloaded and tested. After all, it is a RC, if it blows up in your face, then it is something you will report. At least that is the way it is done in the world of PHP. Several iterations, going from beta (for early adopters only, people living on the edge), to RCs with several iterations, where basically every one out there with a large code base is asked to test it extensively to get to a point where only minor issues remain. The last RC where no critical issues have been found will then be labeled as final x.y.0 release. And that only works, if RCs are actually tested by a large group of people. Best Stefan > > Marcus > > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- Stefan Marr Software Languages Lab Vrije Universiteit Brussel Pleinlaan 2 / B-1050 Brussels / Belgium http://soft.vub.ac.be/~smarr Phone: +32 2 629 3956 Fax: +32 2 629 3525 _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
