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

From Alvaro Herrera
Subject Re: Draft release notes complete
Date
Msg-id 1336655874-sup-5969@alvh.no-ip.org
Whole thread Raw
In response to Re: Draft release notes complete  (Peter Geoghegan <peter@2ndquadrant.com>)
Responses Re: Draft release notes complete
List pgsql-hackers
Excerpts from Peter Geoghegan's message of jue may 10 09:12:57 -0400 2012:
> On 10 May 2012 13:45, Andrew Dunstan <andrew@dunslane.net> wrote:
> > Right, but I think it would be good to identify them explicitly as reviewers
> > if we're going to include the names.
>
> +1. I think we should probably do more to credit reviewers. It's not
> uncommon for a reviewer to end up becoming a co-author, particularly
> if they're a committer, but it's a little misleading to add a reviewer
> after the feature description without qualifying that they are the
> reviewer.

Agreed.

What about crediting patch sponsors (other than the author's employer, I
mean)?  I remember crediting one in a commit message and being told it
wasn't okay.  Is it okay to credit them in the release notes?

--
Álvaro Herrera <alvherre@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support


pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: Draft release notes complete
Next
From: "Kevin Grittner"
Date:
Subject: Re: Gsoc2012 idea, tablesample