On Thu, 2007-07-19 at 16:47 -0400, Tom Lane wrote:
> As already noted, when we set the schedule we were not expecting to
> have so many large patches dropped on us at the very end of the devel
> cycle. What I'd like to think about is how can we avoid *that*
> happening again? 

I think we can set a "Feature proposal" deadline, which is  2-3 months
before "feature freeze" deadline... If someone pushes the proposal and
it is accepted, he/she can begin coding until feature freeze...


PostgreSQL Replication, Consulting, Custom Development, 24x7 support
Managed Services, Shared and Dedicated Hosting
Co-Authors: plPHP, ODBCng - http://www.commandprompt.com/

Attachment: signature.asc
Description: This is a digitally signed message part

Reply via email to