> From: [EMAIL PROTECTED]
...
> suggesting the version change to the OpenSSL library, I'm simply
> trying to address the preconceived notion of major releases with a
> version number of zero implying beta status by non-techies.
Until OpenSSL reaches the point that there will be no incompatible changes
in the API, that view of it being beta status is correct and justified.
"Beta" means more than bug density. It also refers to feature stability.
While ideally, one would hope the design is debugged and stabilized long
before coding occurs, that's rarely the case. It is perfectly reasonable
for a supplier to delete or change features as a result of feedback during
beta, even if the code itself is considered "bug free" (i.e. conforms to
specs, which isn't the same as conforms to expectations).
You owe it to your company to understand that there is a risk that you will
incur future costs in order to change your code to match a changed
interface, and to factor that risk into your decision process. If you need
to address reliability, use real evidence of reliability (such as the
experience of sites currently using OpenSSL in production) instead of
version numbers.
Gary
====================================================================
Ready-to-Run Software, Inc.
Software Porting Specialists.
*****************************
email: [EMAIL PROTECTED] Gary Feldman
fax : 1-978-692-5401 Ready-to-Run Software, Inc.
voice: 1-978-251-5431 11 School Street
www : http://www.rtr.com North Chelmsford, MA 01863
USA
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
