on 4/19/00 1:33 PM, Lynn, James <[EMAIL PROTECTED]> wrote:
> I don't see how this helps your argument since Turbine is alpha. At least
> Cocoon is past a 1.0 release. I understand how you feel confidence in using
> your own alpha product, but as a user/evaluator of the technology, I am not
> prepared to begin an evaluation of your technology until I have confidence
> that any internal models are solidified.
>
> :-)
>
> James
You have a good point in some ways. So, tell me what the difference is
between me rolling a release today and calling it 1.0 vs. what is currently
available? In the end, a number is a number is a number. The code that is
there is what counts and what is there is quite stable.
To me that difference isn't in quality, it is in API stability. We are about
to make a pretty major change to the API (simply re-naming some of the
methods, but it will affect a lot of code) so I'm holding off from rolling a
release because of this. But, if you look at the STATUS.txt document, you
will see that the code is ready to go.
Regardless, even if I decide to roll a 1.0 today, it is just as easy to roll
a 2.0 tomorrow that totally changes everything yet again. So, holding off
because of API stability doesn't really buy you anything except you can
choose to stick at the 1.0 version forever. Commercial companies do this all
the time...except they charge you money when they do it. Gag.
In other words, that "excuse" doesn't really hold up for me because the code
is there and ready to be used in a stable manner AND there is a large
worldwide developer base already using it. 200+ other people don't have a
problem using it. Why should you? :-)
-jon
--
Scarab -
Java Servlet Based - Open Source
Bug/Issue Tracking System
<http://scarab.tigris.org/>
--
----------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
