Hi all,
I suppose the criteria number 1 would be that the code must be open, if
not than I have been said that FoxBugz[1] is ubercool.
Apart from bugzilla that I consider rock solid and working and generally
good choice I'd deploy trac[2] today because it does more than bug
tracking, namely milestones and roadmaps (used by trac itself,
nexenta[3], and django[4]) and I'd also take a look at debian BTS[5]
that has cool email/web/commandline frontend, but two years ago when I
was considering it for my project it was rather hard to deploy &
customize...
HTH,
Martin
P.S. my criteria apart from the license would also include commandline
interface as a priority
[1] http://www.fogcreek.com/FogBugz/
[2] http://trac.edgewall.org/
[3] http://www.gnusolaris.org/gswiki/Bugs
[4] http://djangoproject.com
[5] http://www.debian.org/Bugs/
Stephen Hahn wrote On 2006-07-26 01:51,:
Much like we did during the spring for distributed source code
management, I'd like to start evaluating our options for (at least)
project-level bug tracking on opensolaris.org. In past Solaris
development, people have used BugTraq+ or Bugster, used various open
source bug tracking tools, or written their own small bug trackers,
so we can conclude that there's a wide range of potential needs and
desires we might consider. (Of course, those that depend on a shared
NFS filesystem aren't going to work as well...)
I know that there are both established (Bugzilla, GNATS, ...) and
up-and-coming (Malone (unless it's only a meta-bug-tracking system),
Trac, ...) bug tracking applications. I also know that a lightweight
tracking system is reasonably easy to roll by hand, so I'm sure there
are many others. If you've experiences with any of the ones I
mention, or want to nominate another tool, please share.
Relatedly, if you believe you need a certain form of interaction or
other functionality from the database (singly categorized vs.
multiply categorized bugs, email submission vs. web- or GUI-only,
RSS/Atom feed vs. email notifications, etc.), please mention those as
well.
As we did with the SCM evaluation, we will compile this feedback into
a set of requirements and a list of candidates. Thanks in advance
for your comments.
- Stephen
[] We don't appear to be the only group looking at such an evaluation;
it also appears that the Python developers are contemplating
switching bug trackers:
http://wiki.python.org/moin/CallForTrackers
The announcement section of that page outlines their initial
requirements.
_______________________________________________
tools-discuss mailing list
tools-discuss@opensolaris.org
