Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: neutral (hermes.apache.org: local policy)
Message-ID: <41766D5A.1050100@apache.org>
Date: Wed, 20 Oct 2004 15:51:22 +0200
From: Sylvain Wallez <sylvain@apache.org>
Organization: Anyware Technologies
User-Agent: Mozilla Thunderbird 0.8 (Macintosh/20040913)
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: ECM++
References: <E1CKA1v-00026o-00@deer.gmane.org> <cl5jiu$f8c$2@sea.gmane.org>
 <417661F0.8000708@apache.org>
 <0AA84AF7-2299-11D9-BC00-000A958B684A@outerthought.org>
 <cl5o3c$tsv$2@sea.gmane.org>
In-Reply-To: <cl5o3c$tsv$2@sea.gmane.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Andreas Hartmann wrote:

> Steven Noels wrote:


>> FWIW, the publishing part of Daisy does this as well. But that 
>> shouldn't refrain people from breaking HEAD since we advise people 
>> only to synchronise SVN when we feel comfortable ourselves, and we 
>> package & ship Cocoon in our binary releases rather than requiring 
>> people to install their own version. If a project is willingly 
>> depending on HEAD - *shrug* - we shouldn't make promises to keep HEAD 
>> sane at all times.
>
>
> I agree. And as Carsten said on lenya-dev, the Cocoon project will 
> benefit from other projects beta-testing the trunk.


Sure, and this is a good thing. But that should not refrain us (cocoon 
devs) to do what we feel the need to in the trunk, even if that prevents 
other projects to update their snapshots during an unstability period 
that may exist.

Sylvain

-- 
Sylvain Wallez                                  Anyware Technologies
http://www.apache.org/~sylvain           http://www.anyware-tech.com
{ XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects }