the rule is that we promise backward compatibility except when we need fix a security vulnerability. until we setup a page dedicated to this, make sure you read the changelog ( not just of the current release but all the releases in between the one you upgrade from to the one you upgrade to). Usually backward incompatible issues (if known) are prominently highlighted.
On Aug 30, 2011, at 2:40 PM, Phyo Arkar wrote: > Well , I did the update because i trust web2py's backward > compatibility . Yeah i will never do blind update again (or use update > button on web2py ). > > On 8/31/11, Anthony <abasta...@gmail.com> wrote: >> On Tuesday, August 30, 2011 8:38:14 AM UTC-4, Phyo Arkar wrote: >>> >>> On the mailing list? >>> >>> One problem with mailing list is it is not a forum and it can't have a >>> Sticky feature. Information of last month is totally lost. Most busy >>> people on tight schedule wont have time to dig into pile of posts. >>> >>> So a good place to put it is on the web2py.com home page , make a >>> Notice section . Also in Download page showing that notice. >>> >>> I update from 1.96 tho . >>> >> For changes like this, it would certainly be helpful to post a more >> prominent notice somewhere, as you suggest. But in general, when upgrading, >> it's probably a good idea to review the changelogs between your previous >> version and the new version: http://web2py.com/examples/default/changelog. >> In this case, the change was explained in the changelog. >> >> Anthony >>
