Re: PostgreSQL committer history?

From: Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>
To: Neil Conway <neilc(at)samurai(dot)com>
Cc: "Marc G(dot) Fournier" <scrappy(at)postgresql(dot)org>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Greg Sabino Mullane <greg(at)turnstep(dot)com>, pgsql-advocacy(at)postgresql(dot)org
Subject: Re: PostgreSQL committer history?
Date: 2006-03-09 14:22:43
Message-ID: 1141914173.1716.12.camel@camel
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-advocacy

On Thu, 2006-03-09 at 01:19, Neil Conway wrote:
> On Thu, 2006-03-09 at 01:38 -0400, Marc G. Fournier wrote:
> > Is it as simple as "if nobody objects within 24 hours, apply"?
>
> I don't think the bottleneck is in patch *application* -- applying a
> patch without inspecting its contents doesn't take very much time, and
> there's quite a few community members who could do it. The shortage is
> of people who have the skills to review patches, and I don't see an easy
> way to resolve that.
>

I've often wondered how much it would help to have more committers for
the purpose of having people review & apply smaller patches on their
own, there by reducing the "busy work" from Tom, Bruce, et al who we
really would rather focus on bigger patches. Ie. many of us could
probably review patches for programs like psql, createdb, etc..., is it
really more helpful for those patches to have a followup email from
someone saying "looks good"? Wouldn't it be more productive to have that
follow up email to be a "patch applied" message?

Robert Treat
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL

In response to

Responses

Browse pgsql-advocacy by date

  From Date Subject
Next Message Bruce Momjian 2006-03-09 15:14:28 Re: PostgreSQL committer history?
Previous Message Christopher Browne 2006-03-09 14:04:48 Re: MySQL million tables