Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cocoon-dev@xml.apache.org
From: "Carsten Ziegeler" <cziegeler@s-und-n.de>
To: <cocoon-dev@xml.apache.org>
Subject: RE: Next Release
Date: Tue, 21 Jan 2003 14:44:55 +0100
Message-ID: <LKENJPKDAIKAPKHEOCMMKEPHCFAA.cziegeler@s-und-n.de>
MIME-Version: 1.0
In-Reply-To: <3E2D4A8C.6070901@anyware-tech.com>
Importance: Normal
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset="us-ascii"

Sylvain Wallez wrote:
> 
> We've always said that alpha-status means that APIs can change. So 
> what's the purpose of making an alpha release ?
> 
> Well, this has more to do with marketing and public relations : an alpha 
> release shows to the outside world that some work is happening on 
> something new and that some level of runtime stability has been reached 
> on this new thing.
> 
Absolutely, thanks Sylvain.

Now, guess which question is asked most if you talk about Cocoon: when will
2.1 released? There are many users already using Cocoon 2.1-dev and they
want an official release.
With an alpha release we show that we are trying to reach this. 

> So I'm +0 on an alpha release !
> 
I think, if the flow problems are solved we could also make a beta release
as it seems that most other parts are stable now.

The problem with a release is, that I guess (although I haven't tested it
yet) that the build system is not correctly building the distribution
anymore. And we have to decide what the binary dist will be etc. With
the recent changes (which are excellent) of the blocks and mocks, this
has become a little bit more difficult. So we need some work to be done
here.

Carsten


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org