On Mon, 2007-08-27 at 23:57 +0200, Adrian Aichner wrote:
Hans, the export/import requirement is just a general requirement
against vendor lockin that we should keep in mind.
That's a good point.
Importing legacy data is a thing I could imagine doing myself.
It might be a good idea to start importing recent data and work our
way back.
I think that this should be a manual process anyway, given that there is
no bug history to speak of that is structured.
But hey, the nice thing about import/export interfaces is that once
you tested your im/exporters on a dataset diverse enough you have your
problem solved and don't have to worry whether to import 100 or 1000
defects.
Sure, but there isn't anything to import *from* in this case. Well,
there is the mailing list, and I'm sure different people have different
stashes of bug reports squirreled away for a rainy day, but I'm not sure
that dumping all of these into a bug tracker without actually looking at
them will be a good idea.
> fine for that. Not sure I'm happy to use it for an
open-source project.
Why would you not necessarily recommend it for an open-source project?
I guess I really should have said 'public project'.
What do you see as Trac's pros and cons?
It's pro is that it has a wiki, source browser, and bug tracker all
rolled in one, so to support our in-house development it is nice. In the
wiki you can refer directly to bugs and code revisions which is helpful.
But the bug tracker doesn't really have features that help if you have a
lot of bugs and duplicates. Things like a user account and reporting are
not very well developed, I have the feeling that it doesn't support the
workflow for this. A good example of a large installation would be the
ruby on rails trac:
http://dev.rubyonrails.org/wiki Somehow I always
feel lost in it, though. Looking back at what I wrote I don't really see
a good argument, just a feeling. :-)
> With Gentoo we're using Bugzilla, but that may be overkill
for XEmacs?
Are you suggesting that Bugzilla is the most powerful?
At least as a user (both submitting and managing/resolving bugs) I'm
most happy with Bugzilla. I use Gentoo's bugzilla a lot, and also
Gnome's bugzilla to some extend.
Stephen made some comment about Bugzilla being written in perl and
the
code not seeming easy to maintain.
Are you familiar with some of the internals of Bugzilla?
Nope, not familiar with the internals. As far as I understand it the new
version 3.0 should have a much restructured codebase. New in version
3.0: custom fields, XML-RPC interface (aka XEmacs lisp client ;-),
create and modify bugs by email. Guessing that Steven looked at some 2.x
version, it may actually be worth it to check out 3.0.
Especially any use model shortcomings would be interesting to know.
Anything specific you have in mind here?
Kind regards,
Hans
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta