cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bruno Dumon <br...@outerthought.org>
Subject RE: Proposal: release management guide (was Re: [RT] Versions)
Date Wed, 21 Apr 2004 12:45:20 GMT
On Wed, 2004-04-21 at 09:33, Carsten Ziegeler wrote:
<snip/>
> External Libraries
> ------------------
> Cocoon uses a set of external libraries (like for example Avalon, 
> Xalan or Xerces). Inbetween any release, even patch releases,
> the versions of the external libraries might be updated to any version.

If between patch releases we want to keep everything as compatible as
possible, then we shouldn't upgrade external libraries either (except if
known to be completely safe). Otherwise, all the effort we put into
keeping our own stuff compatible could be lost because of that.

> 
> Therefore if your application is written against a special API of an 
> external library it might be that this API of the external library 
> changes inbetween two Cocoon versions and therefore your application 
> does not work properly anymore (or even does not compile anymore).
> Unfortunately, this issue is out of the scope of Cocoon.

-- 
Bruno Dumon                             http://outerthought.org/
Outerthought - Open Source, Java & XML Competence Support Center
bruno@outerthought.org                          bruno@apache.org


Mime
View raw message