On Wed, Dec 14, 2016 at 02:29:07PM -0800, Josh Berkus wrote: > On 12/14/2016 08:06 AM, Bruce Momjian wrote: > > On Fri, Dec 9, 2016 at 09:46:44AM +0900, Michael Paquier wrote: > >>>> My own take on it is that the release notes are already a massive > >>>> amount of work, and putting duplicative material in a bunch of other > >>>> places isn't going to make things better, it'll just increase the > >>>> maintenance burden. > >>> > >>> This would mean adding literally pages of material to the release notes. > >>> In the past, folks have been very negative on anything which would make > >>> the release notes longer. Are you sure? > >> > >> As that's a per-version information, that seems adapted to me. There > >> could be as well in the release notes a link to the portion of the > >> docs holding this manual. Definitely this should be self-contained in > >> the docs, and not mention the wiki. My 2c. > > > > Yes, that is the usual approach. > > > > So where in the docs should these go, then? We don't (currently) have a > place for this kind of doc. Appendices?
You are saying this is more massive than any other change we have made in the past? In general, what need to be documented? -- Bruce Momjian <br...@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + As you are, so once was I. As I am, so you will be. + + Ancient Roman grave inscription + -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
