Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Message-ID: <405AD716.5010605@vafer.org>
Date: Fri, 19 Mar 2004 12:18:46 +0100
From: Torsten Curdt <tcurdt@vafer.org>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
 rv:1.5) Gecko/20030925
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: [Vote] The right container for 2.2
References: <OFAFF4F043.129DDDA3-ONC1256E5C.00252812@sundn.de>
 <405ACEE3.9040705@hippo.nl>
In-Reply-To: <405ACEE3.9040705@hippo.nl>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

>> So, it seems, the best way to move forward and get into blocks
>> development is to revert to ECM in 2.2 for now. This is a very
>> simple work as 2.2 is container independent. It would 2.2 make
>> immediately usable and compatible to 2.1.x and we could focus
>> our development effort on blocks - which is imho more important
>> than focusing it on container development.

...from what I remember from the discussion, ECM was
not very well suited for the whole blocks implementation.
So I do see this issue related.

I don't really know if reverting will get us somewhere we
want to be. But in fact Fortress seems not to be a smart
choice anymore.

I'd prefer to see where we are going before going anywhere.


So I am currently -0 for reverting to ECM


Eager to see what Pier and Stefano will bring up
--
Torsten