>> Once that's fixed, someone (probably me) needs to propose goals for the >> release. When we have consensus on that, we can start putting out alpha >> releases. > > I met with Christoph Zwerschke the day before yesterday and we talked > a bit about what we think should go into a TG 1.5 release. I agree, > that there shouldn't be too many new features, but there are some > issues, which we already planend for the TG 1.1 release, but nobody > found the time to do and I'd like to adress at least some of them for > TG 1.5. > > I don't have my notes with me now, but I'll try write up our plans > tonight and publish them here. We initially intended to dicuss this > with Ken and the TG2 developers internally first, but I think it's no > harm doing this openly. > >> What I personally took away from the survey was a desire to keep the 1.5 >> release small, so I intend to focus on documentation almost exclusively >> once >> the blockers are closed. > > On the other hand, I don't see much sense in keeping a TG 1 branch if > it doesn't evolve. That would be no fun to work on and without some > fun, nothing gets done.
Thanks guys for the responses, it's good to know that 1.5 will be out in the not too distant future. I also think that incremental small changes are good, there is no need to wait for a huge new killer feature before releasing 1.5. Even if a small 1.5 is out it will send a powerful message that the 1.x branch is not dead and really cool new complicated stuff can go in any time after that, 1.6, etc. 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 -~----------~----~----~----~------~----~------~--~---
