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

From Kenneth Marshall
Subject Re: BugTracker (Was: Re: 8.2 features status)
Date
Msg-id 20060816130933.GO13087@it.is.rice.edu
Whole thread Raw
In response to Re: BugTracker (Was: Re: 8.2 features status)  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
On Wed, Aug 16, 2006 at 06:52:21AM +0200, Peter Eisentraut wrote:
> Tom Lane wrote:
> > that the bug tracker would have to have a reasonable "output" email
> > capability, but I'd not necessarily insist on being able to "input"
> > to it by mail.  Red Hat's present bugzilla system could be described
> > that way --- and while I can't say I'm in love with it, I can deal
> > with it.
> 
> Bugzilla is good in that you need to sign up to report anything (or at 
> least it can be configured that way, not sure), which might reduce the 
> amount of noise.  The other systems that have been mentioned have by 
> design little or no barrier of entry, which doesn't seem to be what we 
> want.
> 
We put an anti-spam solution w/quarantine in front of our RT E-mail
instance (DSPAM) and it is very effective at keeping the cruft out of
the tracking system. You can also do basic processing on incoming
messages to weed out the "non-bugs". We put them in a General start
queue and then move them to other working queues when they meet
whatever threshold you set. The General queue could also automatically
timeout/close tickets that stay in the queue for a certain period of
time.

Ken


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [PATCHES] selecting large result sets in psql using
Next
From: Kenneth Marshall
Date:
Subject: Re: BugTracker (Was: Re: 8.2 features status)