Re: Draft release notes complete

Josh Berkus <josh@agliodbs.com>

From: Josh Berkus <josh@agliodbs.com>

To: Tom Lane <tgl@sss.pgh.pa.us>

Cc: Alvaro Herrera <alvherre@commandprompt.com>, Robert Haas <robertmhaas@gmail.com>, Andrew Dunstan <andrew@dunslane.net>, Peter Eisentraut <peter_e@gmx.net>, Pg Hackers <pgsql-hackers@postgresql.org>

Date: 2012-05-10T22:15:50Z

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 →

Expose track_iotiming information via pg_stat_statements.
- 5b4f34661143 9.2.0 cited
Rewrite GiST support code for rangetypes.
- 80da9e68fdd7 9.2.0 cited
Clean up a couple of box gist helper functions.
- d50e1251946a 9.2.0 cited
Replace the "New Linear" GiST split algorithm for boxes and points with a
- 7f3bd86843e5 9.2.0 cited

> The other problem with such an approach is that section (1) would be
> extremely duplicative of the main release-notes text.  How about a
> hybrid: we continue to identify patch authors as now, that is with names
> attached to the feature/bugfix descriptions, and then have a separate
> section "Other Contributors" to recognize patch reviewers and other
> helpers?

Sounds good to me.


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