I was adding cxf to the site-publish/.htaccess file and was going to go 
ahead and add the others that have graduated, but I want to double check 
something first.

Several of the graduated projects have created their own .htaccess in 
their project directory wrather that use the top level .htaccess.  
Example: servicemix/.htaccess

The question is: is it better to leave it like that or move them to the 
top level .htaccess and completely remove the project directory?  I 
don't really care which, but consistency is probably good and which ever 
way we go, it should be documented in the post graduation checklist 
stuff.

Dan




On Tuesday 22 April 2008, Tony Stevenson wrote:
> Good day,
>
> As part of rolling out the new backup server for the infra team, I
> have discovered that several podling sites are extremely large.
>
> Namely:
>
> 119M    /x1/www/incubator.apache.org/activemq
> 324M    /x1/www/incubator.apache.org/cxf
> 102M    /x1/www/incubator.apache.org/directory
> 166M    /x1/www/incubator.apache.org/lucene.net
> 587M    /x1/www/incubator.apache.org/openjpa
> 299M    /x1/www/incubator.apache.org/servicemix
> 166M    /x1/www/incubator.apache.org/uima
>
>
> I am singling out all sites that over 100MB in size here.  Can someone
> please check the contents of these directories?  I appreciate that
> some of them have graduated from the incubator and as such, these
> datasets are either redundant or should be archived.
>
> I would appreciate a definitive directive as to what should be done
> with these directories.
>
> I will also be updating the documentation on how to handle
> graduation/removal from the incubator.  I'll send an update once this
> has been done too.
>
>
> Cheers,
> Tony
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]



-- 
J. Daniel Kulp
Principal Engineer, IONA
[EMAIL PROTECTED]
http://www.dankulp.com/blog

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to