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 CABUevEx6mWo4NyfOBBfLM9o+6v0BEoVaD7iuB6Zfvf+pySv04A@mail.gmail.com
Whole thread Raw
In response to Re: No Issue Tracker - Say it Ain't So!  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers


On Fri, Jan 8, 2016 at 4:07 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
Magnus Hagander <magnus@hagander.net> writes:
> On Thu, Jan 7, 2016 at 10:57 PM, Joshua D. Drake <jd@commandprompt.com>
>> 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?

Dunno about that.  While a CF manager doesn't necessarily have to have
a commit bit, I think he/she probably does have to be someone who is known
and respected on the -hackers list.  Otherwise, nagging to finish patches
is likely to be ignored or even counterproductive.

I realize now that I caught JDs response slightly out of context. I thought we were talking issue/bugtracker, in which case I think that is needed just as much as it is for a CF manager. As it's basically the same thing just at a different stage.

But that one seems to be more about keeping the todo list on the wiki up to date, in which case I agree, not as much is needed. Because it's more reflecting what's happened, rather than trying to manage process.


--

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: No Issue Tracker - Say it Ain't So!
Next
From: Alvaro Herrera
Date:
Subject: Re: [COMMITTERS] pgsql: Blind attempt at a Cygwin fix