Alvaro Herrera <[EMAIL PROTECTED]> writes:
> In order to make patch review more effective, perhaps we could use some
> tools to help us.  How about

I kinda think this is emphasizing the wrong end of the process.  "Code
everything, then ask for comments" is about as far away from the correct
mindset as one can readily get.

I'd like to see something that emphasizes review and feedback at the
stages of germinal idea, rough functional spec, implementation concept,
etc.  Reviewing the actual code is good too, but if that's the first
stage that you ask for help at, you are off in the wrong direction;
particularly so if you're a larval Postgres hacker.

                        regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?


Reply via email to