Re: Planning incompatibilities for Postgres 10.0

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Planning incompatibilities for Postgres 10.0
Date: 2013-05-28 16:11:45
Message-ID: CA+TgmobUm3PXjYwmoXJP-kJBfcfDmio+z+0DAE31qaYYn402OQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, May 28, 2013 at 11:56 AM, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
>
>>> This argument comes up every couple of years and the people that
>>> are trying to solve the problem by changing the versioning are
>>> ignoring the fact that there is no problem to solve.
>
> We just had this discussion on -advocacy (where it belongs, frankly)

+1.

> a
> couple months ago:
>
> http://www.postgresql.org/message-id/512E8EF8.3000507@agliodbs.com
>
> To sum up: the negatives of changing our version numbering scheme
> outweighed the positives.

And +1 to that, too.

FWIW, I think we may want to consider retitling 9.4 as 10.0, not
because of any binary compatibility break (which, for the record, I
oppose) but because of features. It's a little early to make that
call just yet, of course, but I have a good feeling about this cycle.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Szymon Guz 2013-05-28 16:20:32 Re: potential bug in JSON
Previous Message Stephen Frost 2013-05-28 15:58:49 Re: Extent Locks