Date: Fri, 07 Mar 2008 16:22:24 -0600
From: Robert Lor <Robert.Lor@Sun.COM>
Subject: Re: Commitfest process
In-reply-to: <28031.1204926346@sss.pgh.pa.us>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Heikki Linnakangas <heikki@enterprisedb.com>,
	Alvaro Herrera <alvherre@commandprompt.com>,
	"Joshua D. Drake" <jd@commandprompt.com>,
	PostgreSQL-development <pgsql-hackers@postgresql.org>
Message-id: <47D1C020.6040802@sun.com>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
References: <47D1521E.8090606@enterprisedb.com>
	<20080307101413.7d191e52@commandprompt.com>
	<47D18D80.2050107@enterprisedb.com>
	<20080307105047.2e34a156@commandprompt.com>
	<20080307194612.GB16862@alvh.no-ip.org>
	<47D19E18.4060303@enterprisedb.com>
	<28031.1204926346@sss.pgh.pa.us>
User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728)

Tom Lane wrote:
> This is reasonable for the sort of medium-to-large patch that the author
> has put a lot of time into.  But we also get a lot of small one-off
> patches where it's not so reasonable.  Now of course many of those get
> applied right away, but not all.  One of the services that Bruce's patch
> queue has always performed is making sure stuff like that doesn't fall
> through the cracks.  I don't think a purely author-driven patch queue
> will work to ensure that.
>
> We could combine the ideas: encourage authors to use the wiki, but have
> someone (probably Bruce ;-)) in charge of adding stuff to the wiki if
> the author doesn't.
>   
Stefan Kaltenbrunner said a script can be written to insert an entry 
into the wiki automatically when a new patch comes in. That would be 
ideal and would avoid manual intervention. The author can still update 
the wiki as needed.

http://archives.postgresql.org/pgsql-hackers/2008-02/msg00433.php


Regards,
-Robert