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

From Joshua D. Drake
Subject Re: No Issue Tracker - Say it Ain't So!
Date
Msg-id 568EDF51.8060304@commandprompt.com
Whole thread Raw
In response to Re: No Issue Tracker - Say it Ain't So!  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
Responses Re: No Issue Tracker - Say it Ain't So!  (Magnus Hagander <magnus@hagander.net>)
List pgsql-hackers
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.


JD



-- 
Command Prompt, Inc. - http://www.commandprompt.com/  503-667-4564
PostgreSQL Centered full stack support, consulting and development.
Announcing "I'm offended" is basically telling the world you can't
control your own emotions, so everyone else should do it for you.



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Re: [COMMITTERS] pgsql: Windows: Make pg_ctl reliably detect service status
Next
From: Tom Lane
Date:
Subject: Re: Re: [COMMITTERS] pgsql: Windows: Make pg_ctl reliably detect service status