Re: 9.6 -> 10.0

From: Peter Geoghegan <peter(dot)geoghegan86(at)gmail(dot)com>
To: Josh berkus <josh(at)agliodbs(dot)com>
Cc: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Devrim Gündüz <devrim(at)gunduz(dot)org>, pgsql-advocacy <pgsql-advocacy(at)postgresql(dot)org>
Subject: Re: 9.6 -> 10.0
Date: 2016-05-09 18:26:00
Message-ID: CAEYLb_V5Ys9HVMvhh69fNX4xnsMDB_Pt59+asgnMAU9mTp24Yg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-advocacy

On Mon, May 9, 2016 at 9:16 AM, Josh berkus <josh(at)agliodbs(dot)com> wrote:
>> There is no technical reason to name it 10.0 so why would we?
>
> Because there has never before been a "technical" reason for a major
> version number, so why is that the criterion now?

Exactly.

> We have always been overly conservative about major version numbers.
> The result is having our users talk about "Postgres 9" like there's been
> no significant changes since 9.0.

I think that sticking with the same major version number forever
serves no purpose. Linux changed their approach here, so there were
far fewer 3.* kernels than 2.* kernels. I don't understand how an
insurmountable standard for bumping major versions numbers helps
anything. Linux only got about 4 years out of 3.*, and that change was
for expressly non-technical reasons.

--
Regards,
Peter Geoghegan

In response to

Browse pgsql-advocacy by date

  From Date Subject
Next Message Petr Jelinek 2016-05-09 20:24:25 Re: status/timeline of pglogical?
Previous Message Joshua D. Drake 2016-05-09 17:04:16 Re: status/timeline of pglogical?