public inbox for [email protected]
help / color / mirror / Atom feedFrom: Tom Lane <[email protected]>
To: [email protected]
Cc: Bruce Momjian <[email protected]>
Cc: [email protected]
Subject: Re: Getting a move on for 8.2 beta
Date: Fri, 01 Sep 2006 19:50:56 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
<[email protected]>
Josh Berkus <[email protected]> writes:
> No, it's not. There's a bunch of patches which we had nothing on -- not
> spec, not design draft, not anything -- until we got them on July 20th.
> Our current system is to have only one deadline,
Well, no, it's not. We have told people till we're blue in the face
"post early, post often". Now I will plead guilty to not always having
spent as much time giving feedback on draft patches as I should've, but
the process is pretty clear. As I see it the main problem is people
undertaking patches off in corners somewhere rather than discussing
their work on the mailing lists while they do it.
If you want more process in this we could institute rules like "feature
patches will be rejected out of hand if there wasn't previously a spec
proposal posted to pghackers". I don't think this is really a good
idea, but I'm not sure what else to do.
regards, tom lane
view thread (101+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected]
Subject: Re: Getting a move on for 8.2 beta
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox