Postgres Pro
Downloads
Home   >   mailing lists

Re: should we have a separate page that clearly defines what a minor release is and why it's a good idea to keep up with them? - Mailing list pgsql-docs

From Andrew Hammond
Subject Re: should we have a separate page that clearly defines what a minor release is and why it's a good idea to keep up with them?
Date
Msg-id 5a0a9d6f0702211439n4e8ed03cy3e9aefefc69fdb7b@mail.gmail.com
Whole thread Raw
In response to Re: should we have a separate page that clearly defines what a minor release is and why it's a good idea to keep up with them?  ("Joshua D. Drake" <jd@commandprompt.com>)
List pgsql-docs
Tree view 
On 2/21/07, Joshua D. Drake <jd@commandprompt.com> wrote:
> All users should upgrade to the most recent minor release as soon
> as is reasonable for the environment.  While upgrades always have some
> risk, PostgreSQL minor releases fix only bugs to reduce the risk of
> upgrading. To reduce issues a user may encounter the community strongly

Or...

Minor releases are intended to minimize the risk associated with
change while addressing important stability or security bugs. All
users are strongly encouraged to keep abreast of minor releases as
their maintenance windows permit. ...

Andrew

pgsql-docs by date:

Previous
From: "Joshua D. Drake"
Date:
Subject: Re: should we have a separate page that clearly defines what a minor release is and why it's a good idea to keep up with them?
Next
From: Bruce Momjian
Date:
Subject: Re: should we have a separate page that clearly defines what a minor release is and why it's a good idea to keep up with them?