Re: Release note trimming: another modest proposal
"Jonathan S. Katz" <[email protected]>
| Newsgroups | gmane.comp.db.postgresql.devel.documentation |
|---|---|
| Message-ID | <[email protected]> |
On 2/4/19 5:23 PM, Tom Lane wrote: > "Jonathan S. Katz" <[email protected]> writes: >> On 2/4/19 4:25 PM, Tom Lane wrote: >>> After a bit more thought, I'm inclined to propose that the policy be >>> that we *don't* update the surviving back branches for branch retirement. > >> ...so I guess in turn, we would not update back branches with newer >> releases as well, i.e. adding references about 12 to 10? That makes >> sense, and eases some of the burden on releases. > > No, I definitely didn't have any intention of putting in forward > references to later releases. That seems a bit weird. Agreed. Anyway, I like the overall solution: +1 Thanks for writing the patch, Jonathan
signature.asc
(application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEE+oS2la8r95ogZD/x8QSccp8cZScFAlxYvhQACgkQ8QSccp8c ZSda9A/9EhIo+g8xquNqetv9C5QxvjzMKXqYuVlFvpgU5kPySIOXPTFXTau4LoaV FGsNg/e2XoV/bqaRsw1GWg7sQQLSsE2xJ4h8Idpu6EF4JZJ6/A78BBscdqoOi/PP gxpSsTHZakuXlH/bwKDNX5DMbjTto3JA1GFpe8Bm53um+72E4oG4So7KhjOAc1hX 9XHpknZ1aFyrKFWXH4r5vtz7STkFrQmI+oD80Ym0UzNa/4qNw8aUc7f0NXU1d8qA HDbYzs6Cy5ExKKQ46P0e4qq17hBSUEw9nzyybkYdKB5Bo8DrnOXlPIzTfmlfmFRa 4kgSZuKj4Gen2r48PN6wSZDhk+vPCHQF9zIeKHqb4b2nmmvYa2TlAEhbWJKVpl5k zweSZKhk9SW/1BqdCSZ5AE2kaqhDiKKuADqQ9Yz0f1RezMXhty5YXWHlR5hfoUsr Gn1uW1vig72zG1zkB0UAuWOHRwmfRCsXYe0tweqaGBKfk85TRjfazRTxGxiGzIWs nl0yw0zRnUoDi8w8GkiaCIxDLRJjhGbCSD6zwoxXOVSFXqdBGg9mL0NpUxC7kDZx KLaQOt3+n28ebhwNbVH3whceA7pzVi8plrocxciHgKEpRXxDLYucwPL84RlTtU1s a9kyhVVrLaEdIsMA3Nz9ahi8Ksik01dUDFgdFJ3V+ssuEj0NtZA= =fSyP -----END PGP SIGNATURE-----