[Tracker-discuss] Creating a Jython tracker
Stephen J. Turnbull
turnbull at sk.tsukuba.ac.jp
Tue Feb 5 09:05:05 CET 2008
"Martin v. Löwis" writes:
> In such a scenario, the [Tracker X] supporters would have get
> together and volunteer some people to actually perform the
> necessary setup work, so if [Tracker X] wins, you have already
> volunteers for the first three months into the tracker's life (our
> experience tells that most volunteers will run away within the
> first 6 months after getting this set-up and adopted). For Python,
> it's currently just me that does any maintenance on the tracker.
Yep. This is precisely why I ended up with Roundup: (a) I liked it
already, and (b) I knew I could trust Python to do a good job and
stick with it, so I'd have a good implementation to refer to. By
contrast, I couldn't even get accurate feature lists from the RT,
Trac, and Bugzilla advocates, let alone a commitment to some months of
support. "He who does the work makes the choices."
BTW, Martin, I went with the SVN tip of Roundup (1.4.1 + a couple
patches) instead of the stable 1.3.x that the Python tracker is based
on, and it does a very good job of preventing bad input that results
in tracebacks in the user's browser. For example, I just confirmed that
the "no such user in Actor or Creator" bug is fixed (1.4.x has a nice
Javascript-based selection menu for such input, so you *can't* enter a
nonexistent user AFAICT).
More information about the Tracker-discuss
mailing list