On Wed, Jul 1, 2009 at 9:52 PM, Jorge Vargas<[email protected]> wrote: > > Hello, Just a quick reminder of this. Any opinions on it? if not I'll > choose option A
I have one strong request. Please begin a documentation page in sphinx which explains migration from 2.0.1 to 2.0.2 (if you're targeting 2.0 dev) and 2.0.x to 2.1 if you're targeting 2.1 I want to make sure that the day we release the version that contains this incompatibility I am able to communicate a real upgrade document and not forget this problem. This is a really something we need to do systematically to avoid the problems we had with TG1 before I put in place this procedure. I have another request. Please update a changelog file (either in docs or source code when you add a feature or fix a bug...) so that the releaser can easily prepare a release statement with the info he needs to inform people of what changed. Third, I would prefer a failure that a str(obj)... or if you go the str() way _please_ make it under control of a try/except to make sure any Unicode error is catched properly. Last but not least, did you make sure to add tests to this change to cover the part of the code you changed :) ? Florent. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" 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-trunk?hl=en -~----------~----~----~----~------~----~------~--~---
