On Monday 22 October 2001 10:32 pm, Tom Lane wrote: > Thomas Lockhart <[EMAIL PROTECTED]> writes: > > I think Hiroshi's point is the same as mine: discussions of feature > > changes need to happen on -hackers before being implemented. [snip] > > Subscriptions to other mailing lists should not be required to stay up > > with mainstream development issues.
> Actually, the reason we have an argument now is the other way around: > some non-hackers people complained when the change notice went by. > We do have an obligation to users who don't read -hackers. If they want to deal with development issues, let them subscribe to hackers. Sorry, I know that's more than a little rude. But that _is_ what the hackers list is for, right? 'The developers live there' is the advertisement..... As I'm subscribed to most of the postgresql lists, I sometimes miss which list it's on -- but I'll have to say that I agree with both Thomas and Bruce: the behavior needs to be fixed, AND it needs to be discussed on hackers before fixing. > Given the amount of noise being raised on the issue now, I think the > better part of valor is to revert to the 7.1 behavior and plan to > discuss it again for 7.3. But it's not like Bruce did this with no > warning or discussion. Communications breakdown either way. The warning and discussion was on general -- a bcc to hackers would have been a good thing, IMHO. But that's past. It's mighty close to beta -- is this fix a showstopper? The behavior currently is rather broken according to the results of the discussion on general. Do we really want a whole 'nother major version cycle to pass before this kludge is fixed? Six months to a year down the road? The longer this behavior is in the code, the harder it's going to be to remove it, IMNSHO. -- Lamar Owen WGCR Internet Radio 1 Peter 4:11 ---------------------------(end of broadcast)--------------------------- TIP 4: Don't 'kill -9' the postmaster
