| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Volunteering as Commitfest Manager |
| Date: | 2011-05-25 14:24:03 |
| Message-ID: | 5082.1306333443@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Simon Riggs <simon(at)2ndQuadrant(dot)com> writes:
> I hear that CF manager is a difficult role for a single individual.
> So it makes sense to split that role between multiple people.
> I volunteer to be the CF manager for Replication, and also for
> Performance. ...
> Patches need an eventual committer anyway, so this is a reasonable way
> of having the process be managed by the eventual committer.
ISTM that we really want the CF manager to be somebody who is *not*
directly involved in reviewing or committing patches. It's a distinct
skill set, so there is no reason why it's a good idea for a committer
to do it. And we need to get the CF work load more spread out, not more
concentrated.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Leonardo Francalanci | 2011-05-25 14:29:05 | Re: use less space in xl_xact_commit patch |
| Previous Message | Greg Smith | 2011-05-25 14:17:09 | Re: New/Revised TODO? Gathering actual read performance data for use by planner |