On Mon, Jun 20, 2016 at 4:20 PM, Tom Lane <t...@sss.pgh.pa.us> wrote: > Robert Haas <robertmh...@gmail.com> writes: >> On Mon, Jun 20, 2016 at 4:00 PM, David G. Johnston >> <david.g.johns...@gmail.com> wrote: >>> 10.x is the desired output. > >> 10.x is the output that some people desire. A significant number of >> people, including me, would prefer to stick with the current >> three-part versioning scheme, possibly with some change to the >> algorithm for bumping the first digit (e.g. every 5 years like >> clockwork). > > If we were going to do it like that, I would argue for "every ten years > like clockwork", e.g. 10.0.x is next after 9.9.x. But in point of fact, > Robert, you already made your case for that approach and nobody else > cared for it. Either there's a meaningful difference between the first > and second parts of the number, or there is not. If there is not, why > have separate parts? It can only cause confusion ... as this whole > thread, and its many many predecessors, amply illustrate.
That's not how I remember it. At the Ottawa developer meeting, there were more votes for changing to a two-part versioning scheme than there were for retaining a three-part versioning scheme, but my recollection not overwhelmingly so. I'm pretty sure it was less than a 2/3 majority in favor of changing. Furthermore, essentially everyone in the room, including people who wanted to stick with a three-part scheme, was in favor of the next version's first component being 10. I do not recall there being a strong consensus among the people who wanted the next version to be 10.0.0 on how to decide when to go to 11.0.0, though. Various proposals were offered and most of them got no more than one vote. But saying that nobody other than me thought we should stick with a three-part scheme is revisionist history. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
