Skip site navigation (1) Skip section navigation (2)

Re: CF3+4 (was Re: Parallel query execution)

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: Abhijit Menon-Sen <ams(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: CF3+4 (was Re: Parallel query execution)
Date: 2013-01-16 12:18:04
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
On Wed, Jan 16, 2013 at 1:12 PM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> On 16 January 2013 08:21, Abhijit Menon-Sen <ams(at)2ndquadrant(dot)com> wrote:
>> At 2013-01-16 02:07:29 -0500, tgl(at)sss(dot)pgh(dot)pa(dot)us wrote:
>>> In case you hadn't noticed, we've totally lost control of
>>> the CF process.
>> What can we do to get it back on track?
> "Totally lost control" is an overstatement. The current situation is
> that there are clearly more patches than people working on them; a
> situation that we've been in, with various degrees for all of the last
> 9 years of my involvement with PostgreSQL.
> AFAIK there was no CF manager assigned to Nov2012 CF, so not
> surprising it is off track. Not sure we ever agreed a process for
> assigning CF mgrs, so again, not surprising it is off track.

I don't think we have a process for it, and that's perhaps something
we need to discuss for the future.

> I would like to nominate Craig Ringer to be independent CF mgr for Jan2013 CF.

If he's willing to do that, then +1 from me.

 Magnus Hagander

In response to

pgsql-hackers by date

Next:From: Heikki LinnakangasDate: 2013-01-16 12:18:21
Subject: I broke pg_upgrade for GiST
Previous:From: Andres FreundDate: 2013-01-16 12:16:29
Subject: Re: Curious buildfarm failures (fwd)

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group