Re: Credit in the release notes WAS: Draft release notes complete - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Credit in the release notes WAS: Draft release notes complete
Date
Msg-id 20120513013548.GF21473@momjian.us
Whole thread Raw
In response to Re: Credit in the release notes WAS: Draft release notes complete  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: Credit in the release notes WAS: Draft release notes complete
List pgsql-hackers
On Sat, May 12, 2012 at 09:27:21PM -0400, Andrew Dunstan wrote:
> >Should we go with a single developer per item, and then let people
> >suggest corrections?  With reviewers involved, and often multiple commit
> >messages per release note item, the just isn't enough detail in git logs
> >to reproduce this accurately.  I also over-emphasized new
> >developers/reviewers, but that seems to have distorted the other goals
> >unacceptably.
> 
> Most cases should be pretty clear. Most features have a single major
> commit. The author(s) mentioned there are who should be listed,
> IMNSHO. That might leave a handful of cases where more judgement is
> required.
> 
> We seem to be in danger of overthinking this.

Results have just shown it isn't a simple case.  It is unclear how
important the reviewers were, and how much a committer rewrote the
patch, and the significance of follow-on commits.

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + It's impossible for everything to be true. +


pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: Credit in the release notes WAS: Draft release notes complete
Next
From: Tom Lane
Date:
Subject: WaitLatchOrSocket API needs more thought for socket error conditions