| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
| Cc: | Craig Ringer <craig(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: commit fest schedule for 9.4 |
| Date: | 2013-05-28 23:50:12 |
| Message-ID: | 51A542B4.3090609@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> Shared responsibility is no-one's responsibility. If we are to have
> multiple CF managers, I think it would be good to have one who's mainly
> responsible, and the second one's job is to nag the first manager if
> ernothing happens, and quickly take over if necessary. Ie. a hot standby
> arrangement, rather than two equal CF managers.
Because, of course, we have zero experience coordinating tasks with
other contributors over the internet.
I agree that one CFM needs to be "senior" (there's a lot of judgement
calls involved) but I don't agree that CFM needs to be a single-threaded
task.
Speaking of which, I still need a backup CFM for CF1. Any volunteers?
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2013-05-28 23:51:57 | Re: getting rid of freezing |
| Previous Message | Joshua D. Drake | 2013-05-28 23:37:25 | Re: Planning incompatibilities for Postgres 10.0 |