Hi, I have been doing cleanup and maintenance on the 1.0 branch for some > time now. We need an evolution of the config system to tear it out of > CP2 (thus moving to CP3). This is becoming quite crucial now and will > not wait for an hypothetical 1.2 release.
I had some thoughts on future of 1.x. The general idea is to move towards the 2.0 world, while keeping a stable and backwards-compatible system. 1.1 - Simply switch defaults to sqlalchemy and genshi - can release pretty soon 1.2 - Make ToscaWidgets, AuthKit (depending on TG2 direction), Transactional Middleware defaults, provided decent doc is in place, but leave old stuff (including TGWidgeets) in place. This would seem a good point to attempt CP3 support. I think the important thing about CP3 support is to keep compatibility. Perhaps a little layer that fakes the CP2 config interface, running on top of CP3. Paul --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
