Date: Mon, 12 Nov 2007 19:13:23 -0500
From: Andrew Sullivan <ajs@crankycanuck.ca>
To: Josh Berkus <josh@agliodbs.com>
Cc: pgsql-advocacy@postgresql.org, pgsql-docs@postgresql.org
Subject: Re: Avoiding upgrade backlash
Message-ID: <20071113001323.GA5255@crankycanuck.ca>
Mail-Followup-To: Andrew Sullivan <ajs@crankycanuck.ca>,
	Josh Berkus <josh@agliodbs.com>, pgsql-advocacy@postgresql.org,
	pgsql-docs@postgresql.org
References: <200711121442.31233.josh@agliodbs.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200711121442.31233.josh@agliodbs.com>
User-Agent: Mutt/1.5.13 (2006-08-11)

On Mon, Nov 12, 2007 at 02:42:30PM -0800, Josh Berkus wrote:
> 
> While we are right to choke down abuse of implicit casting, it might be a 
> good idea to give users stronger warnings and instructions.  

I think this is true.  I think it maybe ought to be right at the top of the
notes, and maybe ought to be linked off the announcement of the sort

	Users upgrading from previous releases want to read this <a etc>
	compatibility note</a>
	
I think maybe how Debian handled the notes about kernel changes in the last
stable release would be a good model.  The point there is, _test well_. 
We're doing what we warned you about.

> I'm thinking that we need to warn everyone about:
[&c]

This list seems to miss the main warning needed, which is this in 300 point
bold:

IMPLICIT TYPECASTS HAVE BEEN MOSTLY REMOVED.  TEST YOUR APPLICATION!

A
-- 
Andrew Sullivan
Old sigs will return after re-constitution of blue smoke