Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cocoon-dev@xml.apache.org
From: "Leo Sutic" <leo.sutic@inspireinfrastructure.com>
To: <cocoon-dev@xml.apache.org>
Subject: RE: cocoon deps on avalon (Re: [RT] what cocoon is doing wrong)
Date: Wed, 26 Feb 2003 19:40:52 +0100
Message-ID: <006901c2ddc6$978b5830$0801a8c0@Lagrange>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
In-Reply-To: <b3j0kk$qa6$1@main.gmane.org>
Importance: Normal


Stefano Mazzocchi wrote:
> Recently on avalon-dev I expressed my concerns about their habit of
> moving stuff around for elegance-sake, but I'm starting to think that 
> Cocoon is abusing avalon and this places too much pressure on their 
> shoulders.
> 
> Example: the instrumentation. The Cocoon core is based on code that
has
> never been released. So, Avalon has the right to move it around (and 
> screw us). But I don't think it's *their* fault, it's entirely ours.

I think there's enough blame for both projects. Cocoon has built on
unreleased code, and Avalon has had a terrible track record of releasing
stuff...

I think the meaning behind your comments on dev@avalon were justified,
although I think the situation is not getting worse, it is getting
better.

/LS