Re: BugTracker (Was: Re: 8.2 features status) - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: BugTracker (Was: Re: 8.2 features status)
Date
Msg-id 20060815231526.GB22322@alvh.no-ip.org
Whole thread Raw
In response to Re: BugTracker (Was: Re: 8.2 features status)  ("Jim C. Nasby" <jnasby@pervasive.com>)
Responses Re: BugTracker (Was: Re: 8.2 features status)
Re: BugTracker (Was: Re: 8.2 features status)
List pgsql-hackers
Jim C. Nasby wrote:
> On Tue, Aug 15, 2006 at 10:53:28AM -0500, Kenneth Marshall wrote:
> > RT is easy to setup/configure/use and works well with PostgreSQL
> > as the backend. CPAN uses it for their bug tracker. Was there a
> > list of features and requirements?
>  
> I don't know if we ever came up with one, but I know that the big "deal
> killer" for a bug tracker is that a lot of hackers don't want to be
> forced to use a web interface instead of email. So basically, to be
> accepted, a bug tracker would have to have an effective email interface;
> one that allowed for updates to an issue coming in via email. Sadly, I
> don't think such an animal exists.

We have three candidates already -- debbugs, RT and Gnats.  The first
has the advantage that was written by hackers, for hackers, so it
doesn't have any of the insane "for end users" stuff which annoys so
many people around here ;-) (On the other hand it does have some web
stuff for generating reports, etc).

I haven't used RT much, and I don't know Gnats at all, but I kinda like
(the little I have played with) debbugs.  Apparently it's rather easy to
set up:

http://www.benham.net/debbugs/

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support


pgsql-hackers by date:

Previous
From: "Greg Sabino Mullane"
Date:
Subject: Index bloat and the need to REINDEX
Next
From: Alvaro Herrera
Date:
Subject: Re: Index bloat and the need to REINDEX