Re: Bug tracker tool we need

Brendan Jurd <direvus@gmail.com>

From: Brendan Jurd <direvus@gmail.com>

To: Tom Lane <tgl@sss.pgh.pa.us>

Cc: Greg Smith <greg@2ndquadrant.com>, Robert Haas <robertmhaas@gmail.com>, Magnus Hagander <magnus@hagander.net>, Jay Levitt <jay.levitt@gmail.com>, Alex <ash@commandprompt.com>, Dimitri Fontaine <dimitri@2ndquadrant.fr>, Alvaro Herrera <alvherre@commandprompt.com>, Peter Eisentraut <peter_e@gmx.net>, Pg Hackers <pgsql-hackers@postgresql.org>

Date: 2012-04-18T04:57:09Z

Lists: pgsql-hackers

On 18 April 2012 13:44, Tom Lane <tgl@sss.pgh.pa.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