Re: 9.6 -> 10.0

From: Martín Marqués <martin(at)2ndquadrant(dot)com>
To: Vik Fearing <vik(at)2ndquadrant(dot)fr>, Justin Clift <justin(at)postgresql(dot)org>, Darren Duncan <darren(at)darrenduncan(dot)net>
Cc: pgsql-advocacy(at)postgresql(dot)org
Subject: Re: 9.6 -> 10.0
Date: 2016-05-18 13:07:35
Message-ID: 4d377407-7de9-ac0f-ce59-23d4928dd81e@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-advocacy

El 18/05/16 a las 09:56, Vik Fearing escribió:
> On 18/05/16 14:51, Justin Clift wrote:
>> On 18 May 2016, at 05:35, Darren Duncan <darren(at)darrenduncan(dot)net> wrote:
>>> Following up...
>>>
>>> It appears from today's PgCon meeting that the majority of core developers agree with my simplified proposal, just having MAJOR.PATCH version numbers, and that the plan is to implement that, pending packager/etc feedback.
>>>
>>> https://wiki.postgresql.org/wiki/PgCon_2016_Developer_Meeting#Poll_on_Version_Numbering
>>
>> Looking at the entry there in the wiki, it says:
>>
>> "Simon called for a vote on whether the next release will be 10.0. There was
>> already consensus that the next release is 10.0."
>>
>> For clarity, does that mean this release coming soon is 10.0, or the release
>> after that - sometime in 2017(?) - is 10.0? :)
>
> 9.6 will be 9.6, the next version will be 10.0 (instead of 9.7).

I think that 9.7 will be 10, and not 10.0.

Moving to major.minor versioning.

Regards,

--
Martín Marqués http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Responses

Browse pgsql-advocacy by date

  From Date Subject
Next Message Martín Marqués 2016-05-18 13:14:21 Re: 9.6 -> 10.0
Previous Message Vik Fearing 2016-05-18 12:56:19 Re: 9.6 -> 10.0