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

Re: bugs that have not been replied-to on list

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>
Cc: Jasen Betts <jasen(at)xnet(dot)co(dot)nz>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: bugs that have not been replied-to on list
Date: 2010-04-18 17:12:33
Message-ID: z2w603c8f071004181012t6d68ffbdi36a4011520c777ba@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-bugs
On Sun, Apr 11, 2010 at 7:14 AM, Stefan Kaltenbrunner
<stefan(at)kaltenbrunner(dot)cc> wrote:
> Jasen Betts wrote:
>>
>> On 2010-04-10, Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> wrote:
>>>
>>> Craig Ringer wrote:
>>>>
>>>> Dave Page wrote:
>>>>
>>>>> This basically indicates that we need an issue tracker. There, look -
>>>>> now see what you made me do :-(
>>>>
>>>> Please?!?
>>>>
>>>> I wonder, if EDB just went ahead and set one up, would people start
>>>> using it? I've been tempted to do it myself, but I'm not confident I can
>>>> handle the bandwidth/hosting for a decent tracker with upload capability
>>>> etc.
>>>>
>>>> Or just use Launchpad. It's actually pretty good, and very accessible,
>>>> plus many people already have logins.
>>>>
>>>> I know people are worried it'll just become full of many ignored,
>>>> dupliate or useless reports, but that's what -bugs is anyway; it's just
>>>> less visibly so. Dups and non-bugs are easily closed by the same folks
>>>> who're active on -bugs triaging here.
>>>
>>> the problem is not setting one up (in fact we had multiple serious
>>> attempts at that) but more of how it should interact with the lists, what
>>> tool we should use and "do we even want one". There are tons of discussions
>>> on that very topic in the archives (and also in the wiki).
>>
>> you could set the Bug tracking system to CC every report to the list and
>> possibly have the list refuse posts that are replies to these
>> autoposts so that responses must go through the BTS. alternately you
>> could possibly set something up so that responses also go into bug
>> report on the BTS.
>
> the original plan was to keep the bug report form as it is and just call out
> to the BTS to get a bug id. The form would then just sent the report like it
> does now. The difference would have been that the tracker is subscribed to
> the list and because it "knows" about the bug-id in question it could
> actually track all the responses as if they were created through the BTS.
> That way the only thing left to do in the BTS would have been actually
> marking a bug as closed/todo/whatever - it would be trivial however to
> generate the kind of stuff robert generated manually like "bugs nobody
> replied to yet" or "bug not replied to within X days".
> The prototype we had used bugzilla's xml-rpc interface and the
> email-interface for this but i guess you can do similiar things with other
> trackers.

That all sounds pretty reasonable to me, though I would favor using
something other than Bugzilla for the tracker.  I'm not really sure if
there's anything that I'd consider truly good out there, but I've
always found Bugzilla pretty terrible.  Then again, a bird in the hand
might be worth two in the bush.

...Robert

In response to

Responses

pgsql-bugs by date

Next:From: Peter EisentrautDate: 2010-04-18 18:21:09
Subject: Re: bugs that have not been replied-to on list
Previous:From: Khee ChinDate: 2010-04-17 07:06:05
Subject: Re: BUG #5428: Discrepency in remainder on mod function.

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