>> > > The survey makes it sound like 1.5 is alive again. (This is the >> > > CherryPy 3.0 version). I thought it had been killed? >> >> No, it isn't dead. It's just pining for the fjords! ;) >> >> > I also would like to know the details, especially because the >> > gearshift projecthttp://code.google.com/p/python-gearshift/ aims to >> > do something similar as tg 1.5. What's the latest? :) >> >> One reason for doing this survey was to find out, whether there is >> still interest in further development of a CherryPy based TG version >> or if we just do a couple more maintenance releases of the TG 1.1 >> branch and then let it rest. I would be interested in working on TG >> 1.5 but I am only willing to put effort in this, if there is >> sufficient interest. The TG 1 developer base is very small now >> (basically only three active devs atm), and continuing to evolve the >> TG 1 code base would mean a serious commitment and I'm not even sure >> there is a place for it in the Python web framework world. I certainly >> think that it would not make sense to continue both branches under the >> umbrella of the "TurboGears" moniker, but that's just my opinion. On >> the other hand, I get often get reports from people running still on >> TG 1 and no intention of switching soon. >> >> So, give us some time to evaluate the results of the survey and we'll >> hopefully be able to give a more informed answer to this question >> soon. We will publish our evaluation as soon as possible and probably >> give you all access to the detailed answers (anonymized, of course!). >> >> >> Chris >> >> > Thanks for the response, Chris. The only thing I have to add is an > apology: > > The mail I sent this summer announcing 1.5's demise was premature & horribly > handled. It stemmed from my frustration at not being able to do more to > help get the 1.1 release finalized as well as my perception at the time that > GearShift was quickly evolving all of the features that I wanted to see in > the TG 1.x line. [1] It also didn't help that I was recovering from > (minor) surgery that week & was depressed & on painkillers. > > I'm deeply sorry for that e-mail. It wasn't my call to make & I apologize > for venting my frustration at my own failings so publicly. My only > consolation is that Mark jumped in & pointed out that if anyone else was > interested, they were welcome to join in. > > Please consider that thread to be a poor excuse for a cry for help; that's > all it really amounted to. > > > Thanks for you time, > -Ken
Ken, Chris, Thanks for all the effort that you guys are/were putting into the tg 1.x branch. I'm completely satisfied with tg1 and don't intend to switch at all, I just don't see the benefit. Tg1 is perfect for my project and I see lot of potential for evolving further in the framework of cherrypy and the current tg1 API. It's a healthy situation, the product is robust and reliable and there is lot of room for improvement and adding features. Tg1 couldn't be in a better shape! I try to help as much as my abilities permit, mostly helping others here on the forums and also by sending suggestions/remarks/comments. Once in a while I sent patches, hopefully I'll be able to do more in the future. Keep up the good work! I don't really care if it's called tg 1.5 or gearshift 1.6 or whatever, but it would be great to see the tg 1.5 codebase to evolve further! Cheers, Daniel -- 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 -~----------~----~----~----~------~----~------~--~---
