incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting" <jukka.zitt...@gmail.com>
Subject Re: Incubator dependencies in Apache projects
Date Fri, 26 Sep 2008 21:33:55 GMT
Hi,

On Fri, Sep 26, 2008 at 10:54 PM, Upayavira <uv@odoko.co.uk> wrote:
> We could even require TLP projects that have incubating dependencies
> to include a statement in their releases to that effect: "Should any
> of our incubating dependencies fail incubation, we (the TLP) will take
> responsibility for that code so as to continue supporting our users."

Why?

A TLP will obviously support it's users, but I don't see why it should
take responsibility for the codebase of a failed dependency. Of course
they can do so if it makes sense for the project, but that should not
(and IMHO can not) be a mandate from the Incubator.

For example, Apache Jackrabbit uses the PDFBox library as a dependency
to implement full text indexing of PDF documents. PDFBox is currently
incubating and Jackrabbit will most likely upgrade the dependency as
soon as PDFBox makes its first incubating release. However, there are
no PDF experts in Jackrabbit (that I know of) and there is no way
Jackrabbit could take over the PDFBox code, should PDFBox fail
incubation. Most likely Jackrabbit would just keep using the last
release until some other library with better PDF support appears.

BR,

Jukka Zitting

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Mime
View raw message