Horton

Re: Draft release notes complete

Euler Taveira de Oliveira <euler@timbira.com>

View thread
From: Euler Taveira <euler@timbira.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>, Josh Berkus <josh@agliodbs.com>, Alvaro Herrera <alvherre@commandprompt.com>, PeterEisentraut <peter_e@gmx.net>, Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2012-05-13T00:11:49Z
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

On 12-05-2012 10:27, Bruce Momjian wrote:
> How many names on a single item is ideal?  The activity of reviewers and
> their names on commit messages has greatly expanded the number of
> potential names per item.
> 
Main authors only. Reviewers should be mentioned only in the commit log. If I
coded a feature and Bruce got the idea worked in another patch (that is better
then mine), I think only Bruce should be credited in release notes (but I
could be mentioned in the commit log as the feature designer). However, if I
posted a patch and Robert improved that patch using only 30% of my work, I
should be credited (as coauthor) because he used a considerable part of my work.

I confess that I like the link for relevant commit log in the release notes.


-- 
   Euler Taveira de Oliveira - Timbira       http://www.timbira.com.br/
   PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento