Re: BugTracker (Was: Re: 8.2 features status)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Magnus Hagander <mha(at)sollentuna(dot)net>, "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>, Kenneth Marshall <ktm(at)is(dot)rice(dot)edu>, "Marc G(dot) Fournier" <scrappy(at)postgresql(dot)org>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Mark Kirkwood <markir(at)paradise(dot)net(dot)nz>, Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>, pgsql-hackers(at)postgresql(dot)org, Bruce Momjian <bruce(at)momjian(dot)us>
Subject: Re: BugTracker (Was: Re: 8.2 features status)
Date: 2006-08-18 00:20:22
Message-ID: 910.1155860422@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> Have you tried to use debbugs? I agree with Greg Stark that it's a
> better fit for our current procedure, while enabling better
> traceability.

The principal strike against debbugs seems to be that the source code is
not readily available and/or isn't updated regularly. If we could get
current sources we'd probably end up maintaining our own fork ... OTOH,
given all the enthusiasm being expressed in this thread, somebody would
volunteer to do that no?

Other than that not-small problem, I agree that debbugs seems like an
excellent fit to our existing habits.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2006-08-18 00:33:58 Re: Going for "all green" buildfarm results
Previous Message Satoshi Nagayasu 2006-08-18 00:15:59 Re: pgstattuple extension for indexes