Re: 10.0

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Josh berkus <josh(at)agliodbs(dot)com>, Merlin Moncure <mmoncure(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, 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-13 22:01:41
Message-ID: 20780.1463176901@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> I don't have any strong opinions about this. It's essentially a
> marketing decision, and I'm happy to leave that to others. If and when
> we do change, I'd like to put in a modest request that we add an extra _
> to the branch names, like this: REL_10_0_STABLE. That would mean they
> would sort nicely, which would make my life simpler in a few places in
> the buildfarm code. If not, I'd like a little advance notice so I can
> check all the places where we compare branch names.

If we do decide to change the numbering strategy, there are quite a
few small details that probably ought to be fixed while we're at it.
I think it'd be a good idea to start separating "devel" or "betaN"
with a dot, for instance, like "10.devel" not "10devel". But it's
likely premature to get into those sorts of details, since it's not
clear to me that we have a consensus to change at all.

regards, tom lane

In response to

  • Re: 10.0 at 2016-05-13 21:50:09 from Andrew Dunstan

Responses

  • Re: 10.0 at 2016-05-15 20:41:35 from Jim Nasby

Browse pgsql-hackers by date

  From Date Subject
Next Message Joshua D. Drake 2016-05-13 22:05:14 Re: Lets (not) break all the things. Was: [pgsql-advocacy] 9.6 -> 10.0
Previous Message Tom Lane 2016-05-13 21:55:22 Re: 10.0