Re: 10.0

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Mark Dilger <hornschnorter(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: 10.0
Date: 2016-06-20 20:53:30
Message-ID: 576857CA.3040708@commandprompt.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 06/20/2016 01:41 PM, Alvaro Herrera wrote:
> Tom Lane wrote:
>> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>>> On Mon, Jun 20, 2016 at 4:00 PM, David G. Johnston
>>> <david(dot)g(dot)johnston(at)gmail(dot)com> wrote:

>> If we were going to do it like that, I would argue for "every ten years
>> like clockwork", e.g. 10.0.x is next after 9.9.x. But in point of fact,
>> Robert, you already made your case for that approach and nobody else
>> cared for it.
>
> I voted for this approach initially too, and I think it has merit --
> notably, that it would stop this discussion. It was said that moving
> to two-part numbers would stop all discussion, but it seems to have had
> exactly the opposite effect.
>

Or we could adopt the very reasonable and practical policy of:

The current versioning scheme isn't broke, so we aren't going to fix it.

Put that in the FAQ and wave at it like we do with hints ala Oracle.

It is obvious from this thread alone that there is really no consensus.

Sincerely,

JD

--
Command Prompt, Inc. http://the.postgres.company/
+1-503-667-4564
PostgreSQL Centered full stack support, consulting and development.
Everyone appreciates your honesty, until you are honest with them.

In response to

  • Re: 10.0 at 2016-06-20 20:41:01 from Alvaro Herrera

Responses

  • Re: 10.0 at 2016-06-20 21:08:27 from Robert Haas

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2016-06-20 20:54:04 Re: 10.0
Previous Message David G. Johnston 2016-06-20 20:52:21 Re: parallel.c is not marked as test covered