Re: Draft release notes complete

From: "Greg Sabino Mullane" <greg(at)turnstep(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Draft release notes complete
Date: 2012-05-15 17:03:31
Message-ID: b261aa42fdadead5a3b5921b7423eca4@biglumber.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

> I'd vote for starting a separate thread to solicit people's opinions
> on whether we need names in the release notes. Is there anybody on
> -hackers who would be offended, or would have a harder time persuading
> $BOSS to let them spend time on Postgres if they weren't mentioned in
> the release notes? There'd still be a policy of crediting people in
> commit messages of course, but it's not clear to me whether the release
> note mentions are important to anybody.

Looks like this is mostly answered, and we obviously don't need another
thread, but the answer to the above is "yes".

Release notes are very public, plain text, easy to read, very archived
and searchable. Commit messages might as well be a black hole as far as
visibility to anyone not a developer in the project.

- --
Greg Sabino Mullane greg(at)turnstep(dot)com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201205151301
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----

iEYEAREDAAYFAk+yjFEACgkQvJuQZxSWSsi3gACgmikPzvshZPftTuEdmcB8/Ply
4vMAn1DxvG6hntfxJzWRDdPyWlP5X7WM
=pUbl
-----END PGP SIGNATURE-----

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2012-05-15 17:15:12 Re: Strange issues with 9.2 pg_basebackup & replication
Previous Message Greg Sabino Mullane 2012-05-15 16:59:58 Re: Draft release notes complete