incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eelco Hillenius" <>
Subject Re: Maven 2 repo for incubating project releases?
Date Tue, 01 Aug 2006 04:06:39 GMT
> Most users should not be using Incubator code.  Only those who are committed
> and willing to trust that the project will do well here and eventually
> become an ASF project.
> Remember that most people don't believe that Incubator projects should even
> have a user@ list, only a dev@ list.

I'm new to Apache incubation (and part of project Wicket which just
put up a proposal for incubation). What is very different from what I
expected it to be, is that it seems that the whole process 'feels'
like it is geared towards new projects. Which is surprising given the
number of mature/ proven projects that regularly enter incubation.

Saying that most users should not be using incubator code makes sense
for projects that are in some alpha stage of development. But for more
mature projects (such as Wicket, active for 2.5 years, 6,000 - 12,000
downloads monthly and a couple of thousand more via maven, 17,000+
messages on the user lists alone), doing that would either effectively
shut the project down for more than half a year (and probably loose a
huge customer base) or force developers to branch and maintain a
production release somewhere else. This way of looking at incubation
strikes me being quite inflexible.

Forgive me if I misinterpreted what incubation is all about, but I
expected incubation to be a period where the project being incubated
and Apache see whether they are a good fit to each other. Surely, such
projects should communicate that incubation does not guarantee that
the project will actually be accepted to be an Apache project, or that
the project decides to go on with Apache, but it should communicate a
strong intention from both sides. Otherwise what is the point of even
having a formalized process and involving users in it? Furthermore,
the process of incubation and saying something about the usability of
projects' releases should imho be two different, disconnected aspects.

Just my 2c,


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

View raw message