Hello, I love web2py and normally I just wait a bit when there is new version to make sure I don't spend to much time on version issue.
I also test de trunk once in a wild, but I found difficult to proceed that way. 1) I don't have much time, 2) there is often little issue that will be gone in a release that are actually artifact of development I think. I mean, the developer know that there is most probably something wrong with the new code he produce, but just can't test it in all situation. For sure, tag a beta testing version before releasing could make more work and struggle with version control to make sure patch spread over all branch (trunk, beta), but I think it could be very good to have a beta testing a week before stable. Anyway, I don't have to much problem with the actual practices, but I think beta test could had avoid 1.99.5 for example, since this version has be the beta test version and 1.99.7 the final. Richard On Fri, Aug 31, 2012 at 9:49 AM, Anthony <[email protected]> wrote: > > 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 > > -- > > > > --
