Re: gSoC - ADD MERGE COMMAND - code patch submission - Mailing list pgsql-hackers

From Tom Lane
Subject Re: gSoC - ADD MERGE COMMAND - code patch submission
Date
Msg-id 13074.1278979929@sss.pgh.pa.us
Whole thread Raw
In response to Re: gSoC - ADD MERGE COMMAND - code patch submission  (Greg Smith <greg@2ndquadrant.com>)
Responses Re: gSoC - ADD MERGE COMMAND - code patch submission
List pgsql-hackers
Greg Smith <greg@2ndquadrant.com> writes:
> Tom Lane wrote:
>> Is there a specific period when that's supposed to happen for GSoC
>> students?  Can we arrange for a commitfest to be running then

> The GSoC "Community bonding period" is described at 
> http://googlesummerofcode.blogspot.com/2007/04/so-what-is-this-community-bonding-all.html 
> and what to cover is a near perfect match for things like introducing 
> the patch review and submission process.  This year, the period from 
> when proposals were accepted on April 26th through the official coding 
> start on May 24th were labeled as being devoted to that.  Given the way 
> the release schedule has worked out the last few years, I expect that 
> every year there will be a whole stack of possibly moldy patches sitting 
> in the queue for the first CF of the next version at that point.

Hmm.  Assuming that we manage to keep to an annual release schedule
(no sure thing, since we've never done it yet) what that would mean
is that the students are looking for feedback while most of the key
developers are in heads-down, let's-get-this-release-to-beta mode.
Not sure how well that will work.  Still, we can try it.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: explain.c: why trace PlanState and Plan trees separately?
Next
From: Fujii Masao
Date:
Subject: Re: log files and permissions