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: Bruno Wolff III <bruno(at)wolff(dot)to>
- To: Bruce Momjian <bruce(at)momjian(dot)us>
- Cc: Magnus Hagander <magnus(at)hagander(dot)net>, Andrew Hammond <andrew(dot)george(dot)hammond(at)gmail(dot)com>, pgsql-docs(at)postgresql(dot)org
- 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:01:38 -0600
On Wed, Feb 21, 2007 at 10:07:22 -0500, Bruce Momjian <bruce(at)momjian(dot)us> wrote: > > <P>All users should upgrade to the most recent minor release as soon > as it is available. While upgrades always have some risk, PostgreSQL > minor releases fix only common bugs to reduce the risk of upgrading. > The community considers <i>not</i> upgrading more risky that > upgrading.</P> > > What should change about this text? The "soon as available" seems to be too aggressive to me. This seems to suggest (to me at least) that these upgrades are so important that you might want to skimp on QA to get them in place rapidly. While that may sometimes be true, I don't think it is always the case for everybody.
- Follow-Ups:
- 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: [pgsql-www] 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: