Re: A deprecation policy

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: PG Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: A deprecation policy
Date: 2009-02-11 13:07:34
Message-ID: 603c8f070902110507s69eca029n6774a786fd889905@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Feb 11, 2009 at 2:47 AM, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
> We often discuss changing user-visible behavior of various kinds and are
> usually clueless on the question of "someone might rely on this" or "how
> many people are still using this" etc. Still, it is clearly often useful to
> revise interfaces from time to time.
>
> I have been thinking, with a semi-formal deprecation policy, we could make
> these decisions with more confidence. My proposed policy goes like this:

+1!

This is a very good idea.

...Robert

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Gianni Ciolli 2009-02-11 13:24:31 Re: Optimization rules for semi and anti joins
Previous Message David Fetter 2009-02-11 13:05:20 Re: Optimization rules for semi and anti joins