Re: No Issue Tracker - Say it Ain't So!

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Greg Stark <stark(at)mit(dot)edu>, Robert Haas <robertmhaas(at)gmail(dot)com>, Catalin Iacob <iacobcatalin(at)gmail(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, YUriy Zhuravlev <u(dot)zhuravlev(at)postgrespro(dot)ru>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: No Issue Tracker - Say it Ain't So!
Date: 2016-01-08 15:07:51
Message-ID: 23524.1452265671@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Magnus Hagander <magnus(at)hagander(dot)net> writes:
> On Thu, Jan 7, 2016 at 10:57 PM, Joshua D. Drake <jd(at)commandprompt(dot)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.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2016-01-08 15:11:08 Re: No Issue Tracker - Say it Ain't So!
Previous Message Tom Lane 2016-01-08 15:01:26 Re: pgsql: Blind attempt at a Cygwin fix