Skip site navigation (1) Skip section navigation (2)

Re: Getting a bug tracker for the Postgres project

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Magnus Hagander <magnus(at)hagander(dot)net>, Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>, Kim Bisgaard <kim+pg(at)alleroedderne(dot)adsl(dot)dk>, Greg Stark <gsstark(at)mit(dot)edu>, Joe Abbate <jma(at)freedomcircle(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Getting a bug tracker for the Postgres project
Date: 2011-05-31 16:07:46
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
On Tue, May 31, 2011 at 12:01 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>> On Tue, May 31, 2011 at 10:02 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>>> I kinda wonder why the CF app doesn't work like that, actually.
>>> (Yeah, I know the poor thread linking in the archives is an issue.)
>> I thought this pretty much WAS how the CF app works, except that it's
>> for patches rather than bugs.  Perhaps it could be extended to also
>> track bugs...
> Well, the point is you have to go and manually fool around with the web
> interface to enter something into CF, rather than just cc'ing it on your
> patch or review email.

Oh, I see.  Well, that could probably be changed.  One thing to think
about with the current system is that typically only the most relevant
links get added, as opposed to the entire thread.  Now, the bad news
is that means things often don't get added at all.  The good news is
that typically when people do update it, the add only the relevant
things, thus avoiding filling it up with a massive amount of crap.  I
don't know whether that works out to a bug or a feature.

Robert Haas
The Enterprise PostgreSQL Company

In response to

pgsql-hackers by date

Next:From: Joe AbbateDate: 2011-05-31 16:09:27
Subject: Re: Getting a bug tracker for the Postgres project
Previous:From: Alvaro HerreraDate: 2011-05-31 16:04:07
Subject: creating CHECK constraints as NOT VALID

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group