Re: 9.6 -> 10.0

From: Josh berkus <josh(at)agliodbs(dot)com>
To: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>
Cc: Jim Nasby <jim(at)nasby(dot)net>, Justin Clift <justin(at)postgresql(dot)org>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Devrim GÜNDÜZ <devrim(at)gunduz(dot)org>, pgsql-advocacy <pgsql-advocacy(at)postgresql(dot)org>
Subject: Re: 9.6 -> 10.0
Date: 2016-04-11 18:41:28
Message-ID: 570BEFD8.4080202@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-advocacy

On 04/11/2016 11:32 AM, Joshua D. Drake wrote:
> On 04/11/2016 11:18 AM, Josh berkus wrote:
>
>>>>
>>>> Correct, they are used internally only.
>>>>
>>>
>>> Right and I am not suggesting that we migrate to a policy where we
>>> reference only (or even primarily) the "cute name".
>>
>> So you're thinking just a release name until the number is assigned?
>> Would that benefit anything?
>
> I think there is something to be said for standing in front of a bunch
> of non database people (say... newbie rails developers) and saying:
>
> PostgreSQL is about to release 10.0, otherwise known as Buffalo stampede.

I don't get the value here.

And I spend a lot of time with junior developers. Thing is, the New
Cool Tools (Docker, Rust, Node, GoLang, etc.) *don't* use release names.
This implies that cute release names are passe'.

--
--
Josh Berkus
Red Hat OSAS
(any opinions are my own)

In response to

Responses

Browse pgsql-advocacy by date

  From Date Subject
Next Message Joshua D. Drake 2016-04-11 18:50:20 Re: 9.6 -> 10.0
Previous Message Joshua D. Drake 2016-04-11 18:32:36 Re: 9.6 -> 10.0