Re: pgsql: Remove pre-7.4 documentaiton mentions, now that 8.0 is the oldest - Mailing list pgsql-committers

From Bruce Momjian
Subject Re: pgsql: Remove pre-7.4 documentaiton mentions, now that 8.0 is the oldest
Date
Msg-id 201002241532.o1OFWfF06103@momjian.us
Whole thread Raw
In response to Re: pgsql: Remove pre-7.4 documentaiton mentions, now that 8.0 is the oldest  (Stefan Kaltenbrunner <stefan@kaltenbrunner.cc>)
Responses Re: pgsql: Remove pre-7.4 documentaiton mentions, now that 8.0 is the oldest  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-committers
Stefan Kaltenbrunner wrote:
> Bruce Momjian wrote:
> > Robert Haas wrote:
> >> On Wed, Feb 24, 2010 at 5:03 AM, Stefan Kaltenbrunner
> >> <stefan@kaltenbrunner.cc> wrote:
> >>> Bruce Momjian wrote:
> >>>> Log Message:
> >>>> -----------
> >>>> Remove pre-7.4 documentaiton mentions, now that 8.0 is the oldest
> >>>> supported release.
> >>> per http://wiki.postgresql.org/wiki/PostgreSQL_Release_Support_Policy 7.4 is
> >>> still supported for a few months to come (and will be EOL'd together with
> >>> 8.0). I'm also not really sure why we need to change stuff like that, this
> >>> kind of information might still be useful for somebody trying to upgrade
> >>> from an unsupported release to a supported one.
> >> Yeah.
> >
> > Well, the documentation still exists in the old releases, even 8.4.  The
> > big question is how much back-version information we should keep in our
> > docs, and does it make sense to keep paragraphs around that are only
> > meaningful to < 1% of people reading it.  Some people are saying keep
> > more, some are saying keep less, so I am betting I have hit the proper
> > balance.  ;-)
>
> Well even if it is useful information for only 1% of our readers (which
> given the access stats on the html logs is a HUGE number) and we don't
> have any real maintenance overhead with keeping it (which I kinda doubt
> we have).
>
> And just from looking at some of the hunks in more detail I think we are
> actually removing fairly reasonable information (especially if we are
> talking stuff like behaviour changes) :/

The issue isn't the cost of us maintaining the SGML, it is the cost of
individuals reading it, deciding if it applies to them, and then
skipping to the next paragraph or section.  If we had all this stuff in
one isolated place, we would not have that issue and we could leave it
there forever, but then few people would find it when they needed it.

Also, this stuff is all in the release notes too, which is what people
should be reading for ugprades anyway.  The question is what should be
in the general documentation that everyone reads.

--
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com
  PG East:  http://www.enterprisedb.com/community/nav-pg-east-2010.do
  + If your life is a hard drive, Christ can be your backup. +

pgsql-committers by date:

Previous
From: Stefan Kaltenbrunner
Date:
Subject: Re: pgsql: Remove pre-7.4 documentaiton mentions, now that 8.0 is the oldest
Next
From: momjian@postgresql.org (Bruce Momjian)
Date:
Subject: pgsql: Revert removal of pre-7.4 documenation behavior mentions.