Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
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: Wed, 21 Feb 2007 14:47:30 -0500 (EST)
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. +
- References:
- Prev by Date: 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 by Date: 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 by thread: 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 by thread: 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?
- Indexes: