qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Huston" <shus...@riverace.com>
Subject FW: [DRAFT FOR REVIEW] [ACTION REQUIRED] www.apache.org/dist/<tlp> housekeeping
Date Mon, 06 Jun 2011 16:34:32 GMT
Who has access to qpid's /dist area and can help clean it up?

Thanks,
-Steve

-----Original Message-----
From: Mark Thomas [mailto:markt@apache.org] 
Sent: Friday, June 03, 2011 5:52 PM
To: infrastructure-private@apache.org; pmcs@apache.org
Cc: board@apache.org
Subject: [DRAFT FOR REVIEW] [ACTION REQUIRED] www.apache.org/dist/<tlp>
housekeeping


PMC Members,

If your PMC/Incubator podling does not appear in the lists below please
feel free to ignore this message and apologies for the noise.

TLPs that need to clean up /dist:
abdera, buildr, cassandra, click, cocoon, couchdb, hbase, hive,
jackrabbit, logging, nutch, openwebbeans, perl, portals, qpid, roller,
santuario, shiro, spamassassin, synapse, tcl, thrift, tiles, ws,
xmlbeans, xmlgraphics

TLPs that need to clean up their incubator /dist area:
abdera, buildr, chemistry, esme, libcloud, oodt, river, thrift, uima

Incubator podlings that need to clean up their incubator /dist area:
bval, deltaclound, empire-db, manifoldcf, olio, vcl, whirr, wink


The deadline set below has now passed. You need to clean up your /dist
area(s) asap. If you have any queries, please contact the infrastructure
team.


Mark
on behalf of the ASF Infrastructure Team


On 27/04/2011 13:07, Mark Thomas wrote:
> 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.
> 
> Mark
> 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 http://www.apache.org/dist/. Monitoring of 
>> http://www.apache.org/dist/ [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/www.apache.org/dist/<tlp> on people.apache.org at. Note that any

>> deletions may take up to 24 hours to replicate to 
>> http://www.apache.org/dist In both cases it may take longer for 
>> changes to replicate to mirrors.
>>
>> Old releases removed from http://www.apache.org/dist/ are not lost. 
>> Release are automatically copied to http://archive.apache.org/dist/ 
>> 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] http://www.apache.org/dev/release.html
>> [2] http://people.apache.org/~henkp/tlps/
> 
> 
> 





---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org


Mime
View raw message