It's also worth noting that with this release, 2.0.1 was not released as "stable" but was only ever labeled as a release candidate (rc4 and rc5). The first "stable" release was actually 2.0.2. This is a little different from how it was done in the past (in the past, .1 would have been released as "stable"), yet we see mostly the same behavior (more extensive trial, testing, and bug reporting once the first "stable" release comes out). Perhaps we can improve on this a bit with more explicit advertising about the release candidate.
Anthony On Friday, August 31, 2012 9:49:18 AM UTC-4, Anthony 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 > --
