Re: No Issue Tracker - Say it Ain't So! - Mailing list pgsql-hackers

From Magnus Hagander
Subject Re: No Issue Tracker - Say it Ain't So!
Date
Msg-id CABUevEx3t1NFpdwO6O2_GEB_8j_b8or73iw5BwWkXjS-s7Kn0A@mail.gmail.com
Whole thread Raw
In response to Re: No Issue Tracker - Say it Ain't So!  ("Joshua D. Drake" <jd@commandprompt.com>)
Responses Re: No Issue Tracker - Say it Ain't So!
Re: No Issue Tracker - Say it Ain't So!
List pgsql-hackers


On Thu, Jan 7, 2016 at 10:57 PM, Joshua D. Drake <jd@commandprompt.com> wrote:
On 01/07/2016 12:32 PM, Jim Nasby wrote:
On 1/7/16 1:49 PM, Josh Berkus wrote:
Yeah, we could also get rid of this conversation:

"Here's a patch for X, which is on the TODO list"

"Oh, we've obsolesced that, that was added to the TODO before we had Y"

... by auto-closing TODO items at a certain age.

Even if not auto-closed at least it'd be easy to find old items.

Bonus points if we attract some volunteer project managers that will
keep tabs of all those kinds of things...

/me waves hand....

There are quite a few contributing companies that likely have people that could help out with this in an educated fashion but aren't coders.

Sort of like how they could also have helped out with cf management? 

--

pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: PostgreSQL 9.5.0 regress tests fails with Python 3.5.0
Next
From: Konstantin Knizhnik
Date:
Subject: Re: Optimizer questions