On Friday, August 31, 2012 7:44:31 AM UTC-4, viniciusban wrote:
>
> First of all, I'd like to thank you all. You're making a great job, guys. 
> I see web2py becoming more reliable to bigger projects and I'm very 
> pleased with it. 
> You all rock! :-) 
>
> In spite of this huge effort, isn't it premature to call 2.0.2 or even 
> 2.0.3 stable? I know there were several months of hard work, but if we 
> have bugs detected so fast, we cannot call it stable yet, right? 
>
> Maybe some release candidate call or a pre-release period for tests, 
> before spreading it as stable would help us.
>

Nightly builds have been available throughout development, and there have 
been numerous requests for testers. The fact is, people don't really test 
it and try it out with their existing apps until a full release. In 
practice, the .1 version of any new release is effectively a release 
candidate. Usually bugs are found and fixed quickly, and .2, .3, .4, etc. 
come within a few days, stabilizing fairly quickly.

Anthony 

-- 



Reply via email to