Re: Bug tracker tool we need

From: Brendan Jurd <direvus(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Greg Smith <greg(at)2ndquadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, Jay Levitt <jay(dot)levitt(at)gmail(dot)com>, Alex <ash(at)commandprompt(dot)com>, Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Bug tracker tool we need
Date: 2012-04-18 04:57:09
Message-ID: CADxJZo2NCefSAadExQQ_n=jrN9UdMSKLzjeyfndnhA8KGO58Eg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 18 April 2012 13:44, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> ... I think you'll find a lot of that data could be mined out of our
> historical commit logs already.  I know I make a practice of mentioning
> "bug #NNNN" whenever there is a relevant bug number, and I think other
> committers do too.  It wouldn't be 100% coverage, but still, if we could
> bootstrap the tracker with a few hundred old bugs, we might have
> something that was immediately useful, instead of starting from scratch
> and hoping it would eventually contain enough data to be useful.

Just as a data point, git tells me that there are 387 commits where
the commit log message matches '#\d+', and 336 where it matches 'bug
#\d+'.

Cheers,
BJ

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2012-04-18 04:57:13 Re: patch submission: truncate trailing nulls from heap rows to reduce the size of the null bitmap
Previous Message Greg Smith 2012-04-18 04:01:19 Re: Bug tracker tool we need