-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160
Bruce wrote:
> In summary, names on release note items potentially have the
> following beneficial effects:
>
> * Encouraging new developers/reviewers
> * Encouraging long-established developers
> * Showing appreciation to developers
> * Assisting future employment for developers
> * Helping developers get future funding
> * Assigning responsibility for features
> * Showing Postgres's increased developer base
The only important ones are:
> * Assisting future employment for developers
> * Helping developers get future funding
> * Assigning responsibility for features
> * Assigning blame for feature problems
That last one is not very important either. If there is a bug,
you report it. The original author may or may not handle it.
A better way to state some of the above is:
* Quick cross-reference of a person to a feature.
If I claim to have written ON_ERROR_ROLLBACK, nobody should have
to scroll back through git logs to confirm or deny. (For that matter,
we should do everything possible to prevent anyone from using
git log, especially non-developers, for any meta-information.)
+1 to keep things they way they are. If you were significantly invested
in [re]writing the patch, you get a name. Reviewers, I love you dearly,
but you don't belong next to the patch. Group them all at the bottom
if we must have them there.
- --
Greg Sabino Mullane greg@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201205151259
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----
iEYEAREDAAYFAk+yi3cACgkQvJuQZxSWSsiAcACfYC1HCxbMor/c0EJF6kn+XKc9
kOcAoMn0vnOJLa8+HVz5oWKAZxjkOtQi
=eiUT
-----END PGP SIGNATURE-----
