On Dec 23, 2010, at 8:58 AM, Branko Vukelić wrote: > > On Thu, Dec 23, 2010 at 5:37 PM, Jonathan Lundell <[email protected]> wrote: >> On Dec 23, 2010, at 1:04 AM, cjrh wrote: >>> >>> On Dec 22, 6:05 pm, Thadeus Burgess <[email protected]> wrote: >>>> What I do is if my app works with a certain version, I don't ever upgrade >>>> the web2py unless I need a brand new feature or bugfix that effects me. >>> >>> +1. If you don't need anything new, no point in upgrading. >> >> The problem is that if you *do* need a bugfix, you ordinarily can't get it >> without adopting all the changes since the version you're currently using >> (unless you do your own patching). > > That's another reason why you want to help test the 'release > candidate', right? :)
Seriously: no. That is, if I'm using a release from six months ago, and all I need is a point fix, there's no reason for me to spend any time testing new release candidates. The bulk of web2py users, presumably, are not focused on web2py development; they're simply using web2py as a (very effective) tool to get their real work done. And there's nothing wrong with that.
