Re: Release versioning inconsistency

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: "Dickson S(dot) Guedes" <listas(at)guedesoft(dot)net>
Cc: Marti Raudsepp <marti(at)juffo(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Release versioning inconsistency
Date: 2012-06-21 14:19:31
Message-ID: CABUevEznTG3uBMgOJCXy5HFx0zxp9K48EJ6Gh5hakFHzNXd5cA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Jun 20, 2012 at 1:35 PM, Dickson S. Guedes <listas(at)guedesoft(dot)net> wrote:
> 2012/6/20 Magnus Hagander <magnus(at)hagander(dot)net>:
>> On Wed, Jun 20, 2012 at 11:23 AM, Marti Raudsepp <marti(at)juffo(dot)org> wrote:
>>> On Wed, Jun 20, 2012 at 12:18 PM, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
>>>> (I do believe that using the v9.2.0beta marker is
>>>> *better*, because then it sorts properly. But likely not enough much
>>>> better to be inconsistent with previous versions)
>>>
>>> Good point. Maybe that's a reason to change the versioning scheme and
>>> stick with "9.2.0betaX" everywhere. Including calling the final
>>> release "9.2.0" instead of simply "9.2"?
>>
>> That might actually be a good idea. We can't really change the way we
>> named the betas, but it's not too late to consider naming the actual
>> release as 9.2.0...
>
>
> May be a symlink could be created just do fit the same pattern that other
> versions do and keeps the actual links (for beta) working.

That we can do - in fact, done.

--
 Magnus Hagander
 Me: http://www.hagander.net/
 Work: http://www.redpill-linpro.com/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2012-06-21 14:25:45 Re: Pruning the TODO list
Previous Message Magnus Hagander 2012-06-21 14:17:17 Re: Release versioning inconsistency