Re: Changelog version from 8.1.2 to 9.3.6

On Wed, Jun 15, 2016 at 3:31 AM, Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>
wrote:

> Yogesh Sharma wrote:
> > I have doubt regarding release notes of all versions.
> > As per release notes, below change logs are mentioned in all versions.
> >
> > "(8.3.8,8.4.1,8.2.14) Make LOAD of an already-loaded loadable module
> into a no-op (Tom Lane)"
> > 1. What is meaning of above lines?
> > 2. This changes are implemented only in above versions or is it
> propagated on every above newer
> > versions after that?
> > 3. Why same line is mentioned in the release notes of above
> 8.3.8,8.4.1,8.2.14 versions?
>
> Ad 1:
> As of the cited versions, nothing will be done if you use LOAD to load a
> module
> that is already loaded.
>
> Ad 2:
> The change was a bugfix that was applied to the development version (so it
> is included
> in 9.0 and later) and was backpatched to 8.2, 8.3 and 8.4.
>

​Just to be totally clear on this point.

8.2, 8.3, and 8.4 are all Major releases of the PostgreSQL product. For
most other products it would as if the numbering went from "15, to 16, to
17". The last 8.x release was 8.4 (so, there were 5 major releases that
all shared the same prefix value of 8) and the 9.x series goes from 9.0 to
9.6 (presently in beta). Instead of 9.7 we will be going to 10.0 AND at
the same time modernizing our numbering scheme to lose the prefix-suffix
components. IOW, after 10.0 the next major release will be 11.0. The .0
will increment for minor releases in which we only apply bug-fixes. There
will no longer be a third number.

The rest of Albe's comments apply and are largely driven by this
structure. Each major-release is considered stand-alone and so if the same
basic change is made to more than one major release all of them will have
it documented. But only the initial introduction or application of the
change is documented - any subsequent major or minor release has that
behavior unless a new release note indicates that said behavior changed
again.

David J.