On 1/23/06, Dan Jacob <[EMAIL PROTECTED]> wrote:
I am hoping to get the added responsibility of creating Kid releases. If this happens the release will be more timely.
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 am hoping to get the added responsibility of creating Kid releases. If this happens the release will be more timely.
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 ?
To guarantee stability we have to work closely with all of the projects concerned. Even though we are not directly responsible for those projects we should be brutally aware of what is going on in those projects. For example, I enjoy tormenting myself by watching commits on several projects that I don't actively write code for.
It seems like the individual projects are very responsive to Kevin and the TurboGears crowd in general. There is definitely a trade off between maintaining code yourself and relying on external code. But I think Kevin has it right.
Remember as you assess this project that it is still not a 1.0. It is a work in progress. TG have been taking big strides over the past few months and I expect that it will continue.
-- David
