>>
>
> Yeah, agree. May be we need to put that in the process itself. So no
> patch be submitted unless the idea has been discussed and agreed upon
> to some extent. Of course, few things you will only know once you
> start writing the code. But at least the major points must have been
> accepted by at least one major developer or a committer.
This is little bit problem, because some discussion starts too late -
in commitfest. In my experience +/- 30% of commited patches was zero
response after proposal.
Usually people watching some interesting subset of topics and doesn't
comment "uninteresting" proposals. There are no timeout for rejection
or accepting proposals.
>
> Thanks,
> Pavan
>
> --
> Pavan Deolasee
> http://www.linkedin.com/in/pavandeolasee
>
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers