commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sebb <>
Subject Fwd: [ACTION REQUIRED]<tlp> housekeeping
Date Wed, 27 Apr 2011 13:05:26 GMT
I've cleaned up some old releases (collections-2.1.1, digester-2.0, codec-1.4)

There are still some components with multiple releases (e.g. digester
1.8.1 / 2.1, net 1.4.1/ 2.2) but these are for different Java
versions, and have different major versions.

For all components except DBCP, there is now at only one version of
each component for each current major release.

RMs please remember to remove obsolete versions once a new release has
been out for a few days (to allow mirrors to catch up).

See separate e-mail regarding DBCP numbering.

---------- Forwarded message ----------
From: Mark Thomas <>
Date: 27 April 2011 13:07
Subject: Re: [ACTION REQUIRED]<tlp> housekeeping

PMC members,

Six weeks ago, the infrastructure team sent you the e-mail below. To the
projects that were already following the release guidelines and to those
projects that have since cleaned up their /dist area - thank you. The
infrastructure team really does appreciate you doing this.

Regrettably, a large number of PMCs have chosen to ignore the message
below. To those PMCs, you have one month (until 31 May 2011) to clean up
your dist area or the infrastructure team will simply remove all files
that are more than twelve months old.

on behalf of the ASF Infrastructure Team

On 10/03/2011 08:16, Mark Thomas wrote:
> PMC members,
> As the ASF grows in size, so does the total size of the distribution
> artefacts we ask our mirror community to support for us. The larger this
> total size, the greater the strain on both ASF infrastructure and on the
> mirroring system.
> As per the release guidelines [1], only current releases should be
> available at Monitoring of
> [2] shows that some projects are not
> removing old releases. This is placing an unnecessary strain on both ASF
> infrastructure and on our mirror volunteers.
> Thanks to those PMCs that have been removing old releases from their
> distribution directory. The infrastructure appreciates you keeping on
> top of this.
> PMCs that have not been removing old releases are required to review
> their current distribution directory and remove any old releases.
> - PMCs using svnpubsub should remove old releases via svn.
> - PMCs not using svnpubsub should remove old releases directly from
> /www/<tlp> on at. Note that any
> deletions may take up to 24 hours to replicate to
> In both cases it may take longer for changes to replicate to mirrors.
> Old releases removed from are not lost.
> Release are automatically copied to and
> are never deleted.
> This inevitably raises the question what is a current release and what
> is an old release. To some extent, this varies from project to project
> but typically it amounts to the following:
> a) latest release of the current branch
> b) latest stable release of the current branch
> c) latest stable release of previous branches
> It is hard to give concrete examples that apply to all projects since
> each project is free to use its own release numbering scheme. However, a
> project that includes versions 2.1.0, 2.1.1 and 2.1.2 in its release
> directory almost certainly has some cleaning up to do. A project that
> includes 1.0.6, 1.1.5 and 2.0.7 probably doesn't.
> If you have any questions about how to manage your distribution
> directory please contact the infrastructure team.
> Thanks in advance,
> Mark
> on behalf of the ASF Infrastructure Team
> [1]
> [2]

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

View raw message