Mailing-List: contact dev-help@stdcxx.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@stdcxx.apache.org
Received-SPF: pass (nike.apache.org: local policy)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Subject: RE: moving build result pages to the stdcxx site
Date: Wed, 30 Apr 2008 10:25:43 -0600
Message-ID: 
 <CFFDD219128FD94FB4F92B99F52D0A49010A3762@exchmail01.Blue.Roguewave.Com>
Thread-Topic: moving build result pages to the stdcxx site
Thread-Index: Aciq2sh2T/i2z/DFR4OjJXbCFni/SwAAmQ7A
References: <481642DA.7090909@roguewave.com> <48189682.5080509@roguewave.com>
From: "Eric Lemings" <Eric.Lemings@roguewave.com>
To: <dev@stdcxx.apache.org>

=20

> -----Original Message-----
> From: Martin Sebor [mailto:sebor@roguewave.com]=20
> Sent: Wednesday, April 30, 2008 9:56 AM
> To: dev@stdcxx.apache.org
> Subject: Re: moving build result pages to the stdcxx site
>=20
> This has just become a pressing issue because of the attached
> notice. We have over 5GB of build logs in ~sebor/public_html
> going as far back as June 2007.
>=20
> I have a question in to Tony about size limits in /www and
> under HOME to help us decide what is the better location to
> store this data and what we should delete. My thinking is
> that we want to keep the full set of results for each branch
> in active development going all the way back to the most
> recent release. For each release, we want to keep logs for
> the final release candidate. The question is, what do we do
> for trunk? I'm pretty sure it's not feasible to keep all the
> logs between the last major release (that'd be years).

I'd say archive any and all results that you suspect are not being
used anymore and take them offline.  And be liberal: if someone
does actually need them, we still have archives.

Brad.