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?

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-docs(at)postgresql(dot)org, Andrew Hammond <andrew(dot)george(dot)hammond(at)gmail(dot)com>
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: 2007-02-21 19:47:30
Message-ID: 200702211947.l1LJlUU01020@momjian.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-docs pgsql-www

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(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://www.enterprisedb.com

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

In response to

Browse pgsql-docs by date

  From Date Subject
Next Message Bruno Wolff III 2007-02-21 20:01:38 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?
Previous Message Bruce Momjian 2007-02-21 19:46:19 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?

Browse pgsql-www by date

  From Date Subject
Next Message Bruno Wolff III 2007-02-21 20:01:38 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?
Previous Message Bruce Momjian 2007-02-21 19:46:19 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?