Received: from localhost (maia-4.hub.org [200.46.204.183])
	by postgresql.org (Postfix) with ESMTP id 513499FBDB7
	for <pgsql-docs-postgresql.org@postgresql.org>;
	Wed, 21 Feb 2007 16:01:56 -0400 (AST)
Received: from postgresql.org ([200.46.204.71])
	by localhost (mx1.hub.org [200.46.204.183]) (amavisd-new, port 10024)
	with ESMTP id 89988-03 for <pgsql-docs-postgresql.org@postgresql.org>;
	Wed, 21 Feb 2007 16:01:53 -0400 (AST)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.4
Received: from wolff.to (wolff.to [66.93.197.194])
	by postgresql.org (Postfix) with SMTP id A0DB89FBDB0
	for <pgsql-docs@postgresql.org>; Wed, 21 Feb 2007 16:01:52 -0400 (AST)
Received: (qmail 16711 invoked by uid 500); 21 Feb 2007 20:01:38 -0000
Date: Wed, 21 Feb 2007 14:01:38 -0600
From: Bruno Wolff III <bruno@wolff.to>
To: Bruce Momjian <bruce@momjian.us>
Cc: Magnus Hagander <magnus@hagander.net>,
	Andrew Hammond <andrew.george.hammond@gmail.com>, pgsql-docs@postgresql.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?
Message-ID: <20070221200138.GA9506@wolff.to>
Mail-Followup-To: Bruno Wolff III <bruno@wolff.to>,
	Bruce Momjian <bruce@momjian.us>,
	Magnus Hagander <magnus@hagander.net>,
	Andrew Hammond <andrew.george.hammond@gmail.com>,
	pgsql-docs@postgresql.org
References: <20070221144716.GA21044@svr2.hagander.net>
	<200702211507.l1LF7Me12089@momjian.us>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200702211507.l1LF7Me12089@momjian.us>
User-Agent: Mutt/1.4.2.1i
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=0.048 tagged_above=0 required=5 tests=AWL, BAYES_50
X-Spam-Level: 
X-Archive-Number: 200702/29
X-Sequence-Number: 4160

On Wed, Feb 21, 2007 at 10:07:22 -0500,
  Bruce Momjian <bruce@momjian.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.