| From: | Josh berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Mark Dilger <hornschnorter(at)gmail(dot)com>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, David Fetter <david(at)fetter(dot)org>, Thom Brown <thom(at)linux(dot)com>, Dave Page <dpage(at)pgadmin(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: 10.0 |
| Date: | 2016-05-14 22:48:50 |
| Message-ID: | 5737AB52.4070507@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 05/13/2016 07:18 PM, Mark Dilger wrote:
> My main concern is that a commitment to never, ever break backwards
> compatibility is a commitment to obsolescence. It therefore makes sense to
> reserve room in the numbering scheme to be clear and honest about when
> backwards compatibility has been broken. The major number is the normal
> place to do that.
The problem with that idea is that *minor* backwards compatibility
breakage is much more likely in each-and-every version than major
breakage is at any time in the foreseeable future. The last major
breakage we really had was version 8.3, which if we'd been going by
compatibility should have been 9.0 (also for other reasons).
And if we adopt the "backwards compatibility" approach, then we'll just
be switching from the argument we're having now to the argument of "is
this enough breakage to rate a .0? Yes/No?". Which argument will be
just as long as this one.
So, my vote is now +1 to go to the 2-part numbering scheme.
--
--
Josh Berkus
Red Hat OSAS
(any opinions are my own)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Anderson Carniel | 2016-05-15 01:22:04 | Re: Losing memory references - SRF + SPI |
| Previous Message | Tom Lane | 2016-05-14 22:45:13 | Re: Parallel pg_dump's error reporting doesn't work worth squat |