Dear Lucas, we consider backward compatibility a goal. Every feature described in the manual version 1 (published 2 years ago) should still work as far as we know.
When we accidentally broke backward compatibility, we considered it a bug and fixed it. There are two possibilities: 1) we made a change that broke backward compatibility and we are not aware of it 2) your app has access to web2py internal variables that are not meant to be exposed In case 1, please report the problems. We will fix them in web2py. You do no need to fix them in your apps. If you want to send me your app, confidentially, I will review it for free. In case 2, there is a problem. There is no way a changelog can capture all web2py internal changes. We have a changelog: http://web2py.com/examples/default/changelog all entries are about adding a new feature and or fixing a bug introduced by a newly added feature. The only case we have willingly made a change that broke backward compatibility (happened a couple of times) was to fix a security hole. Massimo On Jan 5, 2:11 am, develucas <develu...@gmail.com> wrote: > Hi everyone > > I'm PM in software company and there is annoying problem for big > teams... > > After my developers team created huge system using web2py it is really > inconvenient for us to find bugs caused by undescribed changes. In my > opinion web2py has big potential, unfortunately it will be wasted > without complete changelog. It should contain every single change > since backward compatibility is not supported. > > This document will save a lot of time for all using web2py > extensively. > > Best Regards
