Mailing-List: contact dev-help@forrest.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@forrest.apache.org
Received-SPF: neutral (herse.apache.org: local policy)
Message-ID: <45DEE24E.8040508@apache.org>
Date: Fri, 23 Feb 2007 12:47:10 +0000
From: Ross Gardler <rgardler@apache.org>
Organization: OSS Watch
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: dev@forrest.apache.org
Subject: Re: [GUMP@vmgump]: Project forrest (in module forrest) failed
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Gump wrote:
> To whom it may engage...
>         
> This is an automated request, but not an unsolicited one. For 
> more information please visit http://gump.apache.org/nagged.html, 
> and/or contact the folk at general@gump.apache.org.

As discussed previously, these gump messages are because Cocoon is not 
building with gump right now (see 
http://vmgump.apache.org/gump/public/forrest/forrest-test/index.html)

We previously agreed to leave the nags in place since it would remind us 
to keep n eye on Cocoon.

However, with the removal of the CLI from Cocoon we cannot run on Cocoon 
head at this time anyway. So even if Cocoon were to start building with 
Gump again we would still fail our tests.

So, do we turn off the gump build for a while, or should we keep the 
nags coming?

Ross