Horton

Re: Credit in the release notes WAS: Draft release notes complete

Josh Berkus <josh@agliodbs.com>

View thread
From: Josh Berkus <josh@agliodbs.com>
To: Bruce Momjian <bruce@momjian.us>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Andrew Dunstan <andrew@dunslane.net>, Robert Haas <robertmhaas@gmail.com>, Alvaro Herrera <alvherre@commandprompt.com>, PeterEisentraut <peter_e@gmx.net>, Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2012-05-13T06:34:35Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Expose track_iotiming information via pg_stat_statements.

  2. Rewrite GiST support code for rangetypes.

  3. Clean up a couple of box gist helper functions.

  4. Replace the "New Linear" GiST split algorithm for boxes and points with a

>> I haven't yet heard any very good argument for deviating from our
>> past practice, which is to credit just the principal author(s)
>> of each patch, not reviewers.
> 
> Is that what people want?  Reviewers are easily removed.  What about
> committers who adjust the patch?

Well, I still think we should give credit to the reviewers ... in a
single section at the bottom, where we list each reviewers' name once.

Reviewers for this release: ...


-- 
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com