From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Christopher Browne <cbbrowne(at)gmail(dot)com> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Josh Berkus <josh(at)agliodbs(dot)com>, PostgreSQL Mailing Lists <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Kudos for Reviewers -- straw poll |
Date: | 2013-06-27 15:56:12 |
Message-ID: | 20130627155612.GA10027@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Jun 27, 2013 at 11:50:07AM -0400, Christopher Browne wrote:
> b) It would be a pretty good thing to mention reviewers within commit notes;
> that provides some direct trace-back as to who it was that either validated
> that the change was good, or that let a bad one slip through.
>
> c) The release notes indicate authors of changes; to have a list of reviewers
> would be a fine thing.
>
> If it requires inordinate effort to get the reviewers directly attached to each
> and every change, perhaps it isn't worthwhile to go to extreme efforts to that
> end.
>
> It could be pretty satisfactory to have a simple listing, in the release notes,
> of the set of reviewers. That's a lot less bookkeeping than tracking this for
> each and every change.
Adding the names to each release note item is not a problem; the
problem is the volume of names that overwhelms the release note text. If
we went that direction, I predict we would just remove _all_ names from
the release notes.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
From | Date | Subject | |
---|---|---|---|
Next Message | Christopher Browne | 2013-06-27 16:00:38 | Re: Min value for port |
Previous Message | Christopher Browne | 2013-06-27 15:50:07 | Re: Kudos for Reviewers -- straw poll |