Re: Bad link for win32/latest
От | Magnus Hagander |
---|---|
Тема | Re: Bad link for win32/latest |
Дата | |
Msg-id | B8163E63-E293-4F6A-995E-13BF3D5E353F@hagander.net обсуждение исходный текст |
Ответ на | Re: Bad link for win32/latest (Magnus Hagander <magnus@hagander.net>) |
Ответы |
Re: Bad link for win32/latest
|
Список | pgsql-www |
On 26 sep 2008, at 13.39, Magnus Hagander <magnus@hagander.net> wrote: > 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? > Marc? Afaik this has not been resolved yet? /Magnus
В списке pgsql-www по дате отправления: