public inbox for [email protected]
help / color / mirror / Atom feedFrom: Bruce Momjian <[email protected]>
To: Joshua D. Drake <[email protected]>
Cc: Bruno Wolff III <[email protected]>
Cc: Magnus Hagander <[email protected]>
Cc: Andrew Hammond <[email protected]>
Cc: [email protected]
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 17:54:23 -0500 (EST)
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
Updated wording:
<P>The PostgreSQL team only adds bug fixes to minor releases. All
users should upgrade to the most recent minor release as soon as
possible. While upgrades always have some risk, PostgreSQL minor
releases fix only frequently-encountered, security, and data corruption
bugs, to reduce the risk of upgrading. The community considers
<i>not</i> upgrading more risky than upgrading.</P>
---------------------------------------------------------------------------
Joshua D. Drake wrote:
> Bruno Wolff III wrote:
> > On Wed, Feb 21, 2007 at 10:07:22 -0500,
> > Bruce Momjian <[email protected]> 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.
>
> Hmmm how about:
>
>
> 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
> suggests reviewing of the release notes for their particular version.
>
>
> --
>
> === The PostgreSQL Company: Command Prompt, Inc. ===
> Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
> Providing the most comprehensive PostgreSQL solutions since 1997
> http://www.commandprompt.com/
>
> Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
> PostgreSQL Replication: http://www.commandprompt.com/products/
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Have you searched our list archives?
>
> http://archives.postgresql.org
--
Bruce Momjian <[email protected]> http://momjian.us
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
view thread (32+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
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?
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox