It seems the problems are not so much in TurboGears itself but with the underlying components - CherryPy in particular recently (see Ian Bicking's comment at http://blog.ianbicking.org/my-cherrypy-rant.html). The problem we have is that although we can control the quality of TG code, we can't control what goes on elsewhere. For example, us poor benighted Windows users haven't had a functioning Toolbox until recently, all because of Kid (and that's only fixed in the SVN, not stable Kid release). I have wanted to add proper localization support to form validation, but that will have to wait until it's in FormEncode(for example, it does not seem to support unicode message strings, which means even lazy_gettext won't work for customizing messages).
The question is: how can we guarantee a stable TurboGears platform even post 1.0 (or for that matter, 2.0) if we cannot guarantee the stability of the underlying components ? Should we enforce a "comply or die" attitude to other projects (if you don't fix your issues, we'll go to Quixote/Cheetah/whatever) ? I don't think that's very workable, and TG is having a positive "rising tide lifts all boats" effect on other projects, but still we are often hamstrung by what happens outside of TG, something Rails and Django don't have to worry about. Any ideas ?
