CIL...

> > If I'm messing up terminology
> 
> Oh, the terminology got messed up long ago.  LOL  :-)  Even the term
> "Release" has different connotations.  It is neutral in the HTTP Server
> project (beta and GA releases, for example), whereas Jakarta refers to
> Nightly builds, Milestone builds and Release builds, so a Release is
> significant.

Sometimes, it's even the case that a milestone == a release.  :)

> 
> We are trying to balance the need to support community development with the
> idea that projects in the incubator shouldn't confuse the public over their
> status by claiming the Apache imprimatur.
> 

And, I support and am not at all trying to undermine that goal in any way.  :)  

I would like to see Beehive deliver to potential users a package that
includes bits we deem complete and for which we guarantee backwards
compatibility.  To me, it seems that calling something "Official"
relative to Beehive is orthogonal to its incubation status.  We
believe that a set of bits are ready to go, though they clearly
originated from an incubating project (thus the location of the web
site, the appropriate notice, and the adjective "incubating" in the
package names) with no claim made to the contrary.  One way to convey
this is by using the "official" adjective, as Derby has done.

The benefit for Beehive is (I believe) that official-ness (again,
relative to the state of code) attracts users and thus contributors
since such a release appears to the observer more complete.  The
notion of completeness is harder to convey in a "milestone".

Another thing that helps is being able to call something 1.0 (or 3.0,
etc) as appropriate.  Are there guidelines for how version numbering
works in Incubator?  Or is this left to the discretion of the project?



>         --- Noel
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to