Re: Contributing code

Tim Allen <tim(at)proximity(dot)com(dot)au> writes:
> Don Y wrote:
>> So, I'll deploy them and get feedback on which features I
>> may need to add (some of the data types are probably a bit
>> too exotic for most users). I figure I can always contribute
>> them just before a release...

> Just before a release would actually be a bad time to contribute the
> code, if you want to get it accepted into PostgreSQL, as the people who
> would be competent to review and potentially accept it all tend to be
> very busy just before a release.

Yeah, I was about to make the same remark. The other thing we see over
and over is that once some idea or code sees the light of day, there are
almost always some better ideas offered by someone in the community, and
thus you need to budget some time for rework in response to comments.

If you're thinking of contributing something major for PG 8.2 (feature
freeze this July) it's already very late to not have at least a complete
design out there for public comment.

regards, tom lane