From: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
---|---|
To: | "Pavan Deolasee *EXTERN*" <pavan(dot)deolasee(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Documentation: references to old versions |
Date: | 2013-02-12 09:32:32 |
Message-ID: | A737B7A37273E048B164557ADEF4A58B057B2195@ntex2010a.host.magwien.gv.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Pavan Deolasee wrote:
> While reading some documentation, I noticed that we have references to
> past releases. For example,
> http://www.postgresql.org/docs/9.2/static/xfunc-c.html mentions "A
> magic block is required as of PostgreSQL 8.2". Sure, this is true even
> as of 9.2 or even 9.3. There are a few more such references that I
> could spot with a simple grep in the doc/src/sgml directory. I wonder
> if this is worth fixing. I don't know sgml enough, but if it supports
> some sort of a meta-tag, then it might help to replace specific
> version references with something like <CURRENT_MAJOR_RELEASE> so that
> the current major version gets substituted when docs for that release
> are built.
I believe that this should remain "8.2".
It tells the reader that the magic block is required for
PostgreSQL since version 8.2, which is saying more than that
it is required in the current release.
Maybe the wording could be changed:
Since PostgreSQL 8.2, a magic block is required.
On the other hand, since 8.2 is desupported, the whole
"as of PostgreSQL 8.2" could be discarded.
I am not sure if <CURRENT_MAJOR_RELEASE> would be very useful.
I think that the documentation should only mention a version number
if the information stays valid.
Otherwise, one should use "the current version" to emphasize that
the statement is not tied to a certain version number.
Yours,
Laurenz Albe
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2013-02-12 09:40:39 | Re: Documentation: references to old versions |
Previous Message | Amit Kapila | 2013-02-12 09:27:51 | Re: Re: Proposal for Allow postgresql.conf values to be changed via SQL [review] |