Re: 10.0 - Mailing list pgsql-hackers

From David G. Johnston
Subject Re: 10.0
Date
Msg-id CAKFQuwaxuG0qVF+RvSmf_emw+SE_x4-Co57sm74ZLoZUdU=Uag@mail.gmail.com
Whole thread Raw
In response to Re: 10.0  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: 10.0  (Gavin Flower <GavinFlower@archidevsys.co.nz>)
Re: 10.0  (Michael Banck <mbanck@debian.org>)
List pgsql-hackers
On Friday, May 13, 2016, Tom Lane <tgl@sss.pgh.pa.us> wrote:
Robert Haas <robertmhaas@gmail.com> writes:
> On Fri, May 13, 2016 at 2:49 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:

> If we don't want to stick with the current practice of debating when
> to bump the same digit, then let's agree that 10.0 will follow 9.6 and
> after that we'll bump the first digit after X.4, as we did with 7.X
> and 8.X.

It was absolute, utter chance that the 7.x and 8.x series both ended
with .4.  I see no reason to turn that into some kind of standard,
especially when it didn't work like that for 6.x or 9.x. 

The underlying premise, for me, of choosing .4 or .5  was that presently we discontinue support after 5 years/releases.  A new .0 would come out just as we discontinue the previous .0

As an added idea, if switching to major.patch, would be to make 10.0.x but then go to 11.x. Though that's somewhat easier cognitively it would probably be harder for developers that just ripping off the bandaid.

David J.

pgsql-hackers by date:

Previous
From: "Joshua D. Drake"
Date:
Subject: Re: 10.0
Next
From: Magnus Hagander
Date:
Subject: Re: 10.0