From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Greg Sabino Mullane <greg(at)turnstep(dot)com> |
Cc: | PostgreSQL Advocacy <pgsql-advocacy(at)postgresql(dot)org> |
Subject: | Re: New versioning scheme |
Date: | 2016-05-12 15:54:16 |
Message-ID: | CA+TgmobpwSCizrOhboL-jDZAxkXjTb-6LHZ3gj1SGfG9JfAHiQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-advocacy |
On Thu, May 12, 2016 at 10:53 AM, Greg Sabino Mullane <greg(at)turnstep(dot)com> wrote:
> Exactly. I think it is time for us to realize that our beloved "major.minor"
> versioning is a failure, both at a marketing and a technical level. It's a
> lofty idea, but causes way more harm than good in real life. People on
> pgsql-hackers know that 9.1 and 9.5 are wildly different beasts. Clients?
> They are running "Postgres 9". So I'm all in favor of doing away with
> major and minor.
I'm not. I've had people be confused about that, but not often.
Maybe my clients are smarter than yours. :-)
In my view, the principal advantage of the current system is that it
slow version number inflation. Bumping the first version number every
year causes you to burn through ten numbers a decade rather than ~2,
and I find that appealing.
But of course that's a matter of opinion.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2016-05-12 15:54:58 | Re: When should be advocate external projects? |
Previous Message | Robert Haas | 2016-05-12 15:44:17 | Re: When should be advocate external projects? |