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 Bruce Momjian
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 200702211947.l1LJlUU01020@momjian.us
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?  (Magnus Hagander <magnus@hagander.net>)
List pgsql-docs
Magnus Hagander wrote:
> I'm not entirely sure about the "frequently-encountered". AFAIK, we fix
> serious stability bugs (or security bugs) even if they are fairly hard
> to trigger. (it's also good to mention that we do patch security bugs, I
> think)

Yes, text updated for that.

--
  Bruce Momjian  <bruce@momjian.us>          http://momjian.us
  EnterpriseDB                               http://www.enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +

pgsql-docs by date:

Previous
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?
Next
From: Bruno Wolff III
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?