commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Cooper" <>
Subject Re: [doc] Cutting the release - should "current" links be provided?
Date Tue, 20 Nov 2007 01:10:34 GMT
You probably want to bring this up with the infrastructure folks. The
use of "current" links was originally requested / recommended by the
folks that manage the mirrors, quite a few years ago. Yours is not the
first comment I've seen that suggests they could cause problems, so it
would be good to get infra to clear this up, one way or the other. I'd
prefer that we keep the links until we have the definitive answer.

Martin Cooper

On Nov 19, 2007 9:43 AM, sebb <> wrote:
> The document
> states in section 7 that symlinks should be created for the "current" release.
> However, AIUI, symlinks don't work for mirrors and rsynch, so these
> are just wasted diskspace on mirrors. [And wasted bandwidth when the
> links are changed.]
> It's also a tedious and error-prone step (unless automated), so
> perhaps it would be best just to drop the links?
> And for some projects (e.g. Collections) there is more than one
> release that could be considered current...
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message