Re: Bad link for win32/latest
- From: "Harald Armin Massa" <haraldarminmassa(at)gmail(dot)com>
- To: "Magnus Hagander" <magnus(at)hagander(dot)net>
- Cc: "Dave Page" <dpage(at)pgadmin(dot)org>, "Marc G. Fournier" <scrappy(at)hub(dot)org>, "Robert Treat" <xzilla(at)users(dot)sourceforge(dot)net>, pgsql-www(at)postgresql(dot)org, "Josh Berkus" <josh(at)agliodbs(dot)com>
- Subject: Re: Bad link for win32/latest
- Date: Fri, 26 Sep 2008 13:46:10 +0200
- Message-id: <7be3f35d0809260446j144ebd1dv4742cfb1edc9d2e4@mail.gmail.com> <text/plain>
my vote:
>>> 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 :-(
I recommend to keep all versions including binaries available. Space is cheap.
Finding a policy is hard.
Finding an old version because only available backup are some rescued
pg_data directories from a harddrive that ended its live in the middle
of a night in the middle of a national holiday is hard.
Of course, officially x.y.n releases are compatible for different n.
But in an emergency I would feel better when not needing this
compatibility.
Harald
--
GHUM Harald Massa
persuadere et programmare
Harald Armin Massa
Spielberger Straße 49
70435 Stuttgart
0173/9409607
no fx, no carrier pigeon
-
EuroPython 2009 will take place in Birmingham - Stay tuned!
Home |
Main Index |
Thread Index