> here are the plans Christoph Zwerschke and I came up with for future > development of the TG 1 branch. > > Feel free to dicuss, give suggestions and comments!
Thanks Chris for this summary, I have just a couple of comments: > TurboGears 1.5 Planning > ======================= > > Team > ---- > > - Ken Kuhlman > - Christoph Zwerschke > - Christopher Arndt > - who else? > > Release manager role shared by Christoph Zwerschke and Chris Arndt > > > Project Infrastructure > ---------------------- > > - Reclaim SVN repository? > - Migrate Trac and SVN to new server Why is this necessary? Can't the 1.x branch stay where it is currently? > - Separate tags/branches/trunk structure for TG1 and TG2 > > - Revive turbogears-trunk and make distinction between users and > development mailing list clear. What exactly needs revival? turbogears-trunk is alive and well AFAIK. Or you mean an ML that is dedicated to the 1.x branch? > > Development Process > ------------------- > > - Commit to 1.5 branch and back-port to 1.1 branch I'd say once 1.5 is out 1.1 users should be encouraged to migrate to it. Back-porting things is a pain and if everyone is told that they should use the latest stable release back-porting will not be so important. I have been using tg from 0.9 or so and have always upgraded to the latest stable release without lot of issues, now I'm at 1.1. If everyone does this we can save lot of time for you guys by not requiring back-ports. > - Only backport to 1.0 branch if *really* necessary (ticket required). I'd say this shouldn't happen and if people are made understand that this indeed is not a priority people will either be happy with the current 1.0 or migrate to 1.5 (once it's out). > - Use more branches > > > New Features > ------------ > > - CP 3.1 support (Ken Kuhlmann) > - Genshi support for TG widgets (Christoph Zwerschke) > - (Start) Sphinx docs (Chris Arndt) > > > Refactoring > ----------- > > - make util module into a a package > - remove feeds package > - deprecate scheduler package Oh wait! And what should we use instead? I'm currently heavily relying on the scheduler module, but if there is a better alternative I'd be happy to migrate. > - reorganize quickstart templates (Chris Arndt, already started) > - database options loading > - lazy template engine loading (Chris Arndt) > > Maybe: > > - refactor commands package If this would make writing custom tg-admin commands easier, I'm all for it. Cheers, Daniel > - refactor i18n package (maybe replace with Babel?) > - rewrite test configuration loading > > Plans > ---- > > - TG 1.1.1 release in 2nd half of November (I have added a milestone > in Trac and started moving tickets into it) > - migration of TG Trac and SVN to dedicated server afterwards > - present development plans on mailing list (this is what you read > now) > - Start discussion about the relationship of TG 1 and TG2 and the > (poor) maintenance state of the TG2 branch. > - TG 1.5 alpha release planned for early January 2010 -- Psss, psss, put it down! - http://www.cafepress.com/putitdown --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
