Re: [tg-trunk] TG2 Status Update - Mar 21, 2011

2011-03-24 Thread Christoph Zwerschke
Thanks. I hope we can then finish the Trac migration this weekend. -- Christoph Am 24.03.2011 05:08 schrieb Mark Ramm: That should be fixed now. Rabbitmq failures at the time of the ticket entry meant they were in mongo but not solr. New updates to allura should mean this will never happen

Re: [tg-trunk] The Future of TG2

2011-03-24 Thread werner
On 24/03/2011 04:21, Michael Pedersen wrote: Before I talk about the future, I'd like to look at the past a little bit. TurboGears has a good history. It's one of the older web frameworks in the Python world, and it managed to have a decent following for a long time. You can see that by

Re: [tg-trunk] The Future of TG2

2011-03-24 Thread Michael Pedersen
On Wed, Mar 23, 2011 at 11:30 PM, Paul Rigor paul.ri...@uci.edu wrote: Do you think mailing list traffic is proportional to TG2 usage? We haven't contacted the ML once we've deployed our web applications. Our group uses TG heavily and perhaps being quite means everything is working just fine

Re: [tg-trunk] The Future of TG2

2011-03-24 Thread Daniel Fetchinson
Flexibility has diluted the main appeal of TG - simplified WEB development. When I started with TG1 there was only 1 set of documentation so there was no way to get derailed by the subtle differences between branches. Assuming 1.0 docs would work in 2.0 or 2.1 is problematic. The original

Re: [tg-trunk] The Future of TG2

2011-03-24 Thread Kevin Horn
I think at the end of this thread, there should definitely be an announcement to the main list regarding these future plans. And Michael, for what it's worth, I think you plan sounds just about perfect, with the exception of you forgetting to mention the CI stuff. :) Kevin Horn On Thu, Mar 24,