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

From Jim Nasby
Subject Re: No Issue Tracker - Say it Ain't So!
Date
Msg-id 568DEB07.6020406@BlueTreble.com
Whole thread Raw
In response to Re: No Issue Tracker - Say it Ain't So!  (Michael Paquier <michael.paquier@gmail.com>)
List pgsql-hackers
On 1/6/16 9:22 PM, Michael Paquier wrote:
> On Thu, Jan 7, 2016 at 9:28 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Jim Nasby <Jim.Nasby@BlueTreble.com> writes:
>>> Somewhat related to that, I don't believe there's any reason why commit
>>> fest managers need to be committers; it seems like the job is really
>>> just about reading through email activity to see where things are at.
>>
>> They don't need to be.
>
> More thoughts on that. I would even think the contrary, someone who
> has just monitored for 1/2 years -hackers and knowing how things are
> handled would be able to do this job as well, the only issue being to
> juggle with many threads at the same time, to be sure that each patch
> status is correct, and to not lose motivation during the CF. The last
> one is the hardest by far.

Sorry, I inadvertently used 'committer' when I should have said 'coder'. 
There's nothing code related about CFM, and I think it's a dis-service 
to the community to have coders serving that role.
-- 
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com



pgsql-hackers by date:

Previous
From: Jim Nasby
Date:
Subject: Re: No Issue Tracker - Say it Ain't So!
Next
From: Tom Lane
Date:
Subject: Re: pg_conversion seems rather strangely defined