Re: Is there a committer in the house?

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bruce Momjian <bruce(at)momjian(dot)us>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Is there a committer in the house?
Date: 2011-07-15 23:02:24
Message-ID: 4E20C700.3060104@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Alvaro,

> The "ready for committer" state does not mean that the committer can
> grab the patch and apply it. Last time I checked, one was still
> expected to review it and take full responsibility for any breakage
> caused by it.

You're absolutely correct. Which is why committer bandwidth is such a
choke point.

--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2011-07-15 23:10:51 Re: isolation tests broken for other than 'read committed'
Previous Message Josh Berkus 2011-07-15 23:01:32 Re: patch: pg_comments system view