I'm going to take a stab in the dark and venture to say that I'm not
the only one using web2py in a "production" environment (i.e. people
other than me are accessing the app) :-P

It seems that with many recent releases there are rather embarrassing
bugs.  The worst was several months ago when authentication was
completely disabled.

Can we adopt a strategy to minimize these potential disasters?  A
sufficient beta channel would do the trick, and a tightening of what
is acceptable as a release build.

Also, how about a security channel so we know when an old version is
unsafe and upgrades are mandatory?  Is there any statement on this
already?

Regards,
Kevin

Reply via email to