Re: Draft release notes complete - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Draft release notes complete
Date
Msg-id 4100.1336747045@sss.pgh.pa.us
Whole thread Raw
In response to Re: Draft release notes complete  (Bruce Momjian <bruce@momjian.us>)
Responses Re: Draft release notes complete
List pgsql-hackers
Bruce Momjian <bruce@momjian.us> writes:
> Let me add that I am concerned about the lack of objectivity in many of
> the suggestions in this thread.  This has prompted me to think that the
> temptation of having names on these release note items is just too
> great, and that the names should be removed.

Er, what?  I have not seen anything in this thread that merits such
an accusation.

> Let me put it this way --- the release notes are read by thousands of
> people.  The benefit individuals gather from their names in the release
> notes is a small part of the overall value provided by the release notes
> to users.  There was a practical need to have names on items in the past
> --- that need is no longer present.

My recollection is that we have been putting the names on the items to
(a) give credit where credit is due, and (b) show that Postgres has a
large and growing development community.  I had never heard the argument
"remember whom to blame for a broken feature" until you raised it
yesterday --- personally, I've always looked in the commit logs if I want
to know something like that.  So I don't see that there's really any
change in the terms of discussion.  It may be that the release notes
aren't the best place for doing either (a) or (b), but I don't agree
that we simply don't need to worry about either anymore.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: Draft release notes complete
Next
From: Magnus Hagander
Date:
Subject: Re: incorrect handling of the timeout in pg_receivexlog