> > > Web2py has so much features and it is impossible to test everything. > > Sorry, but I cannot agree with this statement. Is it the official > position? >
Well, we can probably improve the unit test coverage. And there's been recent talk of developing a test application to check against for some functional testing. But as with any software (particularly as complex as a web framework), it's not possible to test every conceivable permutation of functionality a user might implement. We have to rely on reports of bugs found in the wild to some extent. "Stable" means: "you can download and just use it". Anything different > is "almost stable" or "buggy yet" or, using beautiful words, "release > candidate" or "pre-release version". > We had two (officially labeled) release candidates ( http://code.google.com/p/web2py/source/detail?r=ed41a29eb7c2e283587c141d0464b6c9be68eb0d). Maybe we should change the "Nightly Build" label on the downloads page to "Release Candidate", and perhaps advertise a bit more. Not sure it will help, though, as there were already many requests for testers. What do you suggest? Anthony --
