cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefano Mazzocchi <>
Subject [IMPORTANT] Good names don't change
Date Tue, 02 Oct 2001 12:03:58 GMT
As we start taking about new features and new things that might change
the inner workings of Cocoon, we should *not* call this effort Cocoon3,
and we should stop calling Cocoon, Cocoon2. This leads a sense of
"forking" that is dangerous to the user community.

As we enter the time where Cocoon 2.0 reaches stability and can enter
production, we *must* understand that users (and we all, for that
matter) are investing lots of resources into this, since learning Cocoon
is not exactly a piece of cake.

When Cocoon 2.0 is released, Cocoon 1.x becomes old stuff and will have
a 6 months transition where we'll suggest users to upgrade and then
we'll consider 1.x obsolete.

We'll do 2.0.x releases that incorporate fully-back-compatible bugfixes
and 2.x releases when we'll be forced to do back-incompatible changes
(that we'll document and state clearly, also, if possible, creating
tools that migrate automatically from earlier versions).

The project has grown up.

People are going to use it in production environments and nothing is
going to stop us technically to get to a leading position in the XML
publishing world, we are the only one that can ruin that and one way to
ruin this is to give a sense of "moving target" to users or people that
are deciding whether or not to use Cocoon.

The same thing must be said for Avalon and for all other technologies
that want to be considered "adult" in the software world.

So, I kindly suggest you people to stop using the terms Cocoon2, C2 or
even worse Cocoon3 or C3 after Cocoon 2.0 is released.

Just another thing: the URI

 is *BAD*, we are already creating tons of broken links when we'll have
to remove that and turn back to the *only* cocoon URI which is

but I understand this was done with good intentions and we can fix that
with little hassle.

But, please, from now on, let's be more careful on the future.

So, discussing RT is great and gives the sense that this community is
fun and productive.

Now, it's time to give the impression we are also responsible and
trustful and this starts by behaving as one when controlling the
evolution of the project.

Let's keep up the great work.

Stefano Mazzocchi      One must still have chaos in oneself to be
                          able to give birth to a dancing star.
<>                             Friedrich Nietzsche

To unsubscribe, e-mail:
For additional commands, email:

View raw message