Mats Lidell writes:
Hans> Has any work been done on this already?
I think that there was a go at it for some years ago with some bad
results, which might explain why there isn't a bug tracker now, but I
might be wrong here.
We've had two full-blown trackers, first gnats and then jitterbug.
Both were simply black holes for problem reports.
The issue tracker "roundup" has been suggested.
Roundup is the only one I'm interested in working with, either in
terms of maintaining it or in terms of using it to focus a release, if
people really want me to do the next release. It's very easy to
customize, and I really hate the default organization in all trackers
I've ever used. It also would be easy to prime the database with past
reports, and inject them in batches.
Bugzilla -- fails both the email and XEmacs client tests. We were
offered an email-capable Bugzilla with the code being supported by
SuSE, but my understanding is that Novell has deep-sixed that code.
gnats -- too 16th century.
jitterbug -- maybe it's ok now, but it was a jinx at the time.
Trac -- nobody who has used the MacPorts Trac would be willing to use
Trac. That includes me.
RT -- looks OK in principle, but I will not maintain a big ball of
Perl; we'll need a reliable volunteer for that. I also seem to recall
it doesn't do email very well.
Hans> What would be the next steps for making this happen?
That one, or even better a few, volunteers to maintain the issues in
the tracker in order to unsure the quality.
We need one, no more and no less, really. Having others to help is
fine, but there needs to be one somebody who does the work at a least
a couple times a week and stays on top of the thing. The Python
tracker reports are nice, and something similar probably would do the
trick. It looks mostly automated.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta