incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Johan Compagner" <>
Subject Re: Re: [PROPOSAL] Incubate Wicket
Date Tue, 01 Aug 2006 08:13:14 GMT
The feeling i get from the mail below is that incubator releases are not
really meant for all end users.. You really only want the users that really
knows that it is an incubator release.

But for me wicket-2.0 will be a full release a real release that every user
wicket should be able to use just as they are using wicket 1.2.x now.
And all the time spans for the incubator i here now (6 months is the fastest
many go even to 1 year) then we will release or want to release some or many
releases in that time frame. And as i said i still have the feeling that
shouldn't be done in the incubator time or under the incubator flag.

This is just bad. We need to move on as fast we we developers an put in the
code in to SVN. Not as fast as some legal or administrative tasks has to be


On 8/1/06, Noel J. Bergman <> wrote:
> Dion,
> > What point is there in having something incubated if there are no users?
> We're talking about a balance, and most specifically about ensuring that
> only users who have made a specific and informed decision are using the
> code
> while it is still in the Incubator.  The Apache brand has a value and
> meaning, and users need to know that there is a greater risk of the
> project
> not being around here for them, and that the project is not endorsed.  The
> ASF also needs to prevent brand abuse, which is a distinct possibility,
> and
> some would claim is already a goal of some contributors.
> > Why have releases from within the Incubator at all, in that case?
> :-)  Keep in mind that at one point, *NO* releases were allowed, and that
> I
> was one of the ones who argued the point that you are making.  That we do
> want to permit *SOME* sort of release, in order to allow people who *ARE*
> fully informed and are willing to take the risk to more easily use the
> code
> than having to build it from source control, which is what was previously
> the only way.
> Maven aside, there is no obstacle at all.  Download the code just like you
> would any other package.  For maven, an extra step or so to make sure that
> the person who is executing maven has very specifically and consciously
> opted in to take that specific component from the Incubator.
> And if you'll also notice, I recognize that there are transition issues
> for
> existing projects, particularly existing Open Source projects.
>         --- Noel
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message