Em Quarta 26 Abril 2006 09:59, Tim Lesher escreveu: > > If it changes such that upgrading silently breaks my app in a subtle > way that pre-deployment testing doesn't detect, and then causes me to > have to explain to a CFO at 8:30 AM why we can't bill for anything in > the past three months, why, yes, I'd rather have worked around a > missing feature. > > Yes, this has happened to me. (Curse you, Sybase!) :-)
I am just wondering *why* would you upgrade at 8h30 at the deployment day after running all your test suite and doing integration tests and functionality checks with the older version. Documented or not, you still have to test (the several kinds of tests) your application. Develop against a moving target isn't easy. Also, if you need some specific fix, you can grab it from TG's repository: this is one of the best things about open source. Anyway, I will really like when we have more docs -- I worked with software documentation for years... -- even if they aren't stable. I'm a great fan of docstrings, comments, etc. Nothing prevented people from documenting the code while they coded and, unfortunately, this is not a common practice in any programming language that I know :-( -- Jorge Godoy <[EMAIL PROTECTED]> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears -~----------~----~----~----~------~----~------~--~---
