El domingo, 29 de junio de 2014 23:25:20 UTC+2, Niphlod escribió: > > - where to place and how to organize the tests > > a few slices and projects exist on testing web2py. Unfortunately there's > yet no "recommended way" officially proposed by web2py >
So some examples would be nice > > >> - version upgrades, and specifically if an upgrade of your app goes >> hand-in-hand with an upgrade of web2py (should I release the app bundled >> with web2py to solve that?) >> > > you upgrade web2py to benefit from fixed bugs and new features. As long as > your app can accomodate for those, I don't see a real reason why NOT > upgrade . > I remember one upgrade of web2py that required some tweaking of the app, so I don't want the users to upgrade web2py whenever they want. But my repo contains only the app, so from time to time it would be nice if they upgrade. -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
