Yeah, don't worry I know , web2py is most backward compatible framework in the know. Just need some prominent annoucement section on the web pages , and it will even more popular. *Regular website update*
For announcement , only Prominent Changes such as : - Major changes/improvement - Security Alerts - Backward Incompatible changes I know alot of users of web2py in my country , most of the I introduced to. even my closest friends who use web2py , dont bother to join web2py mailing list. They will be much less likely to read mailing list ferequently. I believe whoever post once in this mailing list is less than 20% of actual users out there. Those people will just Read the web site , and use web2py's Update button in admin view. On 8/31/11, Massimo Di Pierro <[email protected]> wrote: > 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 <[email protected]> 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 >>> > >
