Re: Prepping to break every past release...

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: Simon Riggs <simon(at)2ndQuadrant(dot)com>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Prepping to break every past release...
Date: 2009-03-11 14:41:40
Message-ID: 1236782500.26259.0.camel@jd-laptop.pragmaticzealot.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, 2009-03-11 at 08:41 +0000, Simon Riggs wrote:
> On Wed, 2009-03-11 at 08:33 +0200, Peter Eisentraut wrote:

> The first step is to record incompatibilities as they occur and record
> them somewhere, so that people can say "that'll break my app". Often the
> first people hear about these things is when we compile the release
> notes, which is far too late either to complain or to fix.
>

That is a simple modification of the release notes and something that
really should be done regardless of a deprecation policy.

Joshua D. Drake

--
PostgreSQL - XMPP: jdrake(at)jabber(dot)postgresql(dot)org
Consulting, Development, Support, Training
503-667-4564 - http://www.commandprompt.com/
The PostgreSQL Company, serving since 1997

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Stark 2009-03-11 14:45:31 Re: idea, proposal: only preloadable libraries (conditional load)
Previous Message Simon Riggs 2009-03-11 14:18:43 Re: idea, proposal: only preloadable libraries (conditional load)