Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Message-ID: 
 <1E0CC447E59C974CA5C7160D2A2854EC097DC7@SJMEMXMB04.stjude.sjcrh.local>
From: "Hunsberger, Peter" <Peter.Hunsberger@stjude.org>
To: <dev@cocoon.apache.org>
Date: Thu, 25 Mar 2004 09:08:00 -0600
Subject: RE: [RT] On building on stone
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-SEF-FD9E3BCC-24E9-4B6F-96E-FFC4B78D445A: 1
content-class: urn:content-classes:message
Thread-Topic: [RT] On building on stone
Thread-Index: AcQSTz4FQnXdlro4SNq8B8gSHaQIIQAKsn8A
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N

Jorg Heymans <jh@domek.be> writes:

> >=20
> > Cocoon needs a rock solid core.
> >=20
> > Solid in both technical, social and legal way.
> >=20
>=20
> Stefano,
>=20
> - i am considering cocoon as the basis for a new product in=20
> the next 3=20
> months. It will be based on 2.1.x, a possible future core migration=20
> makes me nervous to say the least. My previous decision last=20
> year in may=20
> to use the 2.0.x branch for my project backfired when i now=20
> see how much=20
> easier things could have been with flow, woody etc.

Hmm, 2.1.4 and even 2.1.3 are really very stable and very usable.  2.1.5
should clean up forms, but I can't see why you need to worry about what
blocks will bring?

Basically, when Stefano and Pier talk about building for the future with
blocks I think they are talking about a time when Cocoon is a much
bigger and more complex beast than it is now.  We can see the start of
the problem now, so they plan to avoid it in the future.  However,
unless you do a lot of changing configurations for Cocoon this shouldn't
be an issue for you in the short term; once you get a solid
configuration for Cocoon you just keep running with it.

Yes, new features will keep on coming, in the mean time, Cocoon still is
a better way to go than the alternatives.  So, don't hold back, take
advantage of what Cocoon already offers and know that some time in the
future it will be even easier to plug new components in and out (i.e.;
without having to rebuild Cocoon).