Re: Bad link for win32/latest - Mailing list pgsql-www

From Magnus Hagander
Subject Re: Bad link for win32/latest
Date
Msg-id 48DCC9EC.4030502@hagander.net
Whole thread Raw
In response to Re: Bad link for win32/latest  ("Dave Page" <dpage@pgadmin.org>)
Responses Re: Bad link for win32/latest  ("Harald Armin Massa" <haraldarminmassa@gmail.com>)
Re: Bad link for win32/latest  (Magnus Hagander <magnus@hagander.net>)
List pgsql-www
Dave Page wrote:
> On Wed, Sep 24, 2008 at 6:46 AM, Magnus Hagander <magnus@hagander.net> wrote:
>> Robert Treat wrote:
>>> On Tuesday 23 September 2008 14:08:58 Josh Berkus wrote:
>>>> Folks,
>>>>
>>>> http://www.postgresql.org/ftp/binary/latest, which should point to
>>>> 8.3.4, is still pointing to 8.3.3.
>>>>
>>> Actually the whole main directory needs to be updated, it isn't listing 8.3.4
>>> or 8.2.10... http://wwwmaster.postgresql.org/ftp/
>> I've updated svr1, I *think* that's the master and it should push out
>> soon :-)
>>
>> I can never remember, on what schedule do we remove old versions? Did we
>>  say "keep current and one older"? In that case, there is some removing
>> to do as well... In binary, for example, we have 8.2.5, 6, 7, 8, 9 and
>> 10 ATM - that just seems like a waste of space to me. For source, we
>> have 8.2.7, 9 and 10, and in the 8.3 series 8.3.1, 3 and 4. We also have
>> source/OLD which has 8.3.0, 8.2.5 and 8.2.6. All in all, seems we're not
>> very consistent :-(
>>
>> If we don't have a policy, let's make one - get your arguments out :-)
> 
> Marc was managing that (and the symlinks) iirc. I'm not sure what
> rules he was working to.
> 

Marc? What's the usual deal?

//Magnus




pgsql-www by date:

Previous
From: "Dave Page"
Date:
Subject: Re: Upgrading pgFoundry
Next
From: "Harald Armin Massa"
Date:
Subject: Re: Bad link for win32/latest