Re: unresolved bugs

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: Greg Stark <gsstark(at)mit(dot)edu>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: unresolved bugs
Date: 2010-01-07 00:52:07
Message-ID: 1262825527.8287.415.camel@jd-desktop.unknown.charter.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, 2010-01-07 at 00:45 +0000, Greg Stark wrote:
> On Wed, Jan 6, 2010 at 11:09 PM, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
> > Oh, wow, I didn't realize it was time for another round of this. Wheeeee!
> >
>
> Actually I suspect it is time.
>
> My preferences have changed. While they used to go something like
> debbugs > RT > nothing > bugzilla they now go something like debbugs >
> RT > bugzilla > nothing. That is, even though bugzilla is possibly my
> least favourite open source bug tracking system it's still better than
> continuing the way we are. We've been pretty lucky so far, in part due
> to Tom and others being remarkably diligent but it's only a matter of
> time until we forget or miss a critical report. And from a PR point of
> view it just looks terrible.
>
> So in short while I still think debbugs is the best approach to this
> I've seen at this point *any* free software based solution is fine
> with me.

I have been looking at roundup fairly extensively. It is what
bugs.python.org uses.

Joshua D. Drake

--
PostgreSQL.org Major Contributor
Command Prompt, Inc: http://www.commandprompt.com/ - 503.667.4564
Consulting, Training, Support, Custom Development, Engineering
Respect is earned, not gained through arbitrary and repetitive use or Mr. or Sir.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Stark 2010-01-07 00:55:46 Re: unresolved bugs
Previous Message Robert Haas 2010-01-07 00:52:02 Re: Serializable Isolation without blocking