On Thu, Aug 21, 2008 at 7:28 AM, Christopher Arndt <[EMAIL PROTECTED]> wrote: > > Christoph Zwerschke schrieb: >> Updating the CHANGELOG is already on my todo list, since a couple of >> other things have been fixed so we should think about making another >> bugfix release soon. (Maybe not 1.0.6 but 1.0.5.1, because the fixes are >> not so large and we will run out of version numbers too quickly?). > > Maybe we should have a definition of what constitutes a point release > (1.0.*.x) and what a full 1.0.x release? Anyway, I don't see why we > should stop at 1.0.9. 1.0.10 seems a perfectly valid version number to > me (not that I *want* to maintain TG 1.0.x for that long). > > Florent, do you have any opinion on this (as the official 1.x release > manager)? > > On a related matter, why does the release.py file in the 1.1 branch > state "1.5" as the version number and the 1.5 branch has "1.6"? I'm > confused. > > Chris >
The 1.1 & 1.5 branch name versus 1.5 & 1.6 milestone confusion is partly my fault. Florent had decided that the next point release should be 1.5 & was most of the way through that change when I popped back up to say that CherryPy 3.1 support was nearing. That raised the question of whether changing the template & ORM defaults is enough change to justify a half point release bump, or if that should be reserved for the larger CP3 change. It's a good time to have this discussion. I'll post my detailed opinions on the release schedule shortly. -Ken --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
