Re: PostgreSQL committer history?

From: "Marc G(dot) Fournier" <scrappy(at)postgresql(dot)org>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Greg Sabino Mullane <greg(at)turnstep(dot)com>, pgsql-advocacy(at)postgresql(dot)org
Subject: Re: PostgreSQL committer history?
Date: 2006-03-09 05:38:53
Message-ID: 20060309013825.B1178@ganymede.hub.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-advocacy

On Thu, 9 Mar 2006, Bruce Momjian wrote:

> Greg Sabino Mullane wrote:
> [ There is text before PGP section. ]
>>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>>
>>> Right. It is a case where the volume of patches just overwhelms us and
>>> we give them commit access. It isn't "trust", and the only downside I
>>> see to commit vs. non-commit users is the delay in getting things into
>>> CVS. The delay used to be 24-48 hours, but as my responsibilities have
>>> grown, the delay has grown as well. I am not sure how to fix that.
>>
>> Delegate that responsibility to the others that have commit access. If
>> that's not enough, grant some more people commit access so they can
>> apply the already approved patches. And stop traveling all over the
>> world so much. :)
>
> The patch queues are open and committers are encourages to apply them.
> Neil and Tom do it sometimes. I then remove the item and update any
> TODO entries.

Is it as simple as "if nobody objects within 24 hours, apply"?

----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email: scrappy(at)hub(dot)org Yahoo!: yscrappy ICQ: 7615664

In response to

Responses

Browse pgsql-advocacy by date

  From Date Subject
Next Message Neil Conway 2006-03-09 06:19:06 Re: PostgreSQL committer history?
Previous Message Christopher Kings-Lynne 2006-03-09 05:26:35 TurboDBAdmin