It seems like adding "Incubating" to the name of the release would prevent this from smelling like official ASF code, or even from smelling like fully-baked code. I think we're all for that -- our main goal is to fulfill the requirements for exiting the Incubator, not to languish there doing non-official releases. Concurrent with that, we hope that releasing stable code will help us build dev community (along the lines of what Dan wrote on this thread earlier).

Noel asked earlier:

You did do http://cvs.apache.org/dist/incubator/beehive/v1.0m1/, so what is
the "this release" to which you refer?

I just meant whatever "release" we were debating calling an "Official Release". Eddie suggested in beehive-dev a few days ago that we should put out a release of NetUI/Controls, so people could try out stable versions of those two technologies without waiting until WSM can obtain/pass the JSR181 TCK.

Rich


Cliff Schmidt wrote:

On 6/8/05, Noel J. Bergman <[EMAIL PROTECTED]> wrote:
FWIW, versioning schemes such as:

M.mQB

where M == major, m == minor, Q in [D:Development, A:Alpha, B:Beta,
R:Release], and B == Build# encode the release type.  I supposed that 1.0m1
represents a milestone.

In any event, I'm sure that people can come up with some perfectly sane
scheme to label.  The only thing is that we don't want it to smell like
official ASF code until after the project graduates the Incubator.

How about something like:
Apache {projectname} (Incubating) vM.mQB ?

e.g. "Apache Beehive (Incubating) v1.0R555"

We already require the word "incubating" in the filenames, but things
like TheServerSide posts wouldn't normally mention this.  I'm
suggesting that the name of the release always include "(Incubating)"
wherever it is mentioned.

Cliff

---------------------------------------------------------------------
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