Re: Release versioning inconsistency - Mailing list pgsql-hackers

From Dickson S. Guedes
Subject Re: Release versioning inconsistency
Date
Msg-id CAHHcrepioJNmtCaf0RwLJEnjU_MzmpPPzpZLCHEwnfmDWg7KYA@mail.gmail.com
Whole thread Raw
In response to Re: Release versioning inconsistency  (Magnus Hagander <magnus@hagander.net>)
Responses Re: Release versioning inconsistency
List pgsql-hackers
2012/6/20 Magnus Hagander <magnus@hagander.net>:
> On Wed, Jun 20, 2012 at 11:23 AM, Marti Raudsepp <marti@juffo.org> wrote:
>> On Wed, Jun 20, 2012 at 12:18 PM, Magnus Hagander <magnus@hagander.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.

I'm using the same pattern in `pgvm` [1]  and it is failing to fetch
beta versions :(


[1] https://github.com/guedes/pgvm/blob/master/include/sites


regards
-- 
Dickson S. Guedes
mail/xmpp: guedes@guedesoft.net - skype: guediz
http://guedesoft.net - http://www.postgresql.org.br


pgsql-hackers by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: Release versioning inconsistency
Next
From: Simon Riggs
Date:
Subject: Re: [ADMIN] pg_basebackup blocking all queries with horrible performance