From: | David Fetter <david(at)fetter(dot)org> |
---|---|
To: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Josh berkus <josh(at)agliodbs(dot)com>, 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-17 14:51:18 |
Message-ID: | 20160517145118.GA1437@fetter.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, May 17, 2016 at 01:45:09PM +0800, Craig Ringer wrote:
> On 14 May 2016 at 02:49, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> > * This year's major release will be 9.6.0, with minor updates 9.6.1,
> > 9.6.2, etc. It's too late to do otherwise for this release cycle.
> >
> > * Next year's major release will be 10.0, with minor updates 10.1,
> > 10.2, etc.
> >
> > * The year after, 11.0. Etc cetera.
> >
> >
> Yes. Please!
>
> I get tired of explaining to people that PostgreSQL "9.x" isn't a thing,
> that yes, 9.3 and 9.4 really _do_ have incompatible data directories and
> replication protocols, and that when the docs say "major version" they
> don't mean "major version as you might actually expect" but "first two
> version number parts".
>
> Lets get rid of this user-baffling wart.
Hear, hear!
Sadly, we're too late for 9.6, but we can start with 10.0 and finish
this silliness once and for good.
Cheers,
David.
--
David Fetter <david(at)fetter(dot)org> http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfetter XMPP: david(dot)fetter(at)gmail(dot)com
Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate
From | Date | Subject | |
---|---|---|---|
Next Message | Jim Nasby | 2016-05-17 14:58:18 | Re: Does Type Have = Operator? |
Previous Message | Jim Nasby | 2016-05-17 14:38:28 | Re: HeapTupleSatisfiesToast() busted? (was atomic pin/unpin causing errors) |