On Jan 22, 2008 6:07 AM, Christoph Zwerschke <[EMAIL PROTECTED]> wrote:
[...] > How do we want to proceed? First create a stable TG 1.1 version again in > the 1.1 branch, and then create a new 1.2 branch for switching to > CheerryPy 3, or should we already work on CherryPy 3 in the current TG > 1.1 branch? How big would the change be, what does it entail? The plan is as follow: - sync 1.1 with all the latest changes we did in 1.0 that were not ported to 1.1 yet (all the encode stuff per example) - then in parallell: break config out of CP2 and instrumentize CP3 config in our own config class _and_ make sure the test system works on CP3 (ATM our tests are really coupled with CP2 internals) - the stabilize somewhat and release rc version. I'll take time to create tickets and road map on trac... Florent. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
