Re: Release versioning inconsistency - Mailing list pgsql-hackers

From Magnus Hagander
Subject Re: Release versioning inconsistency
Date
Msg-id CABUevEx5_Q2MwbG3hGTyzBs6f_SQ41mqojs-U3W2pvpaENK3_w@mail.gmail.com
Whole thread Raw
In response to Release versioning inconsistency  (Marti Raudsepp <marti@juffo.org>)
Responses Re: Release versioning inconsistency  (Marti Raudsepp <marti@juffo.org>)
List pgsql-hackers
On Wed, Jun 20, 2012 at 10:28 AM, Marti Raudsepp <marti@juffo.org> wrote:
> Hi list,
>
> The recent 9.2 beta releases have used a slightly different numbering
> scheme than all previous releases.
>
> It used to be that tarballs for version $VER were always available at:
>  http://ftp.postgresql.org/pub/source/v$VER/postgresql-$VER.tar.bz2
>
> However, the new releases now use "v9.2.0beta2" for the directory
> name, but "9.2beta2" in the tarball file. No big deal for most people,
> but it will confuse people who have scripts to download PostgreSQL
> tarballs automatically (e.g. packagers).
>
> For example:
>  http://ftp.postgresql.org/pub/source/v9.2.0beta2/postgresql-9.2beta2.tar.bz2
>
> Is there any reason behind this change?

Not behind the first one. I believe that's just me and a bad memory -
I got it wrong. (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)

For beta2, the only reason was to keep it consistent with beta1.

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


pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: [PATCH 10/16] Introduce the concept that wal has a 'origin' node
Next
From: Marti Raudsepp
Date:
Subject: Re: Release versioning inconsistency