OpenSSL versioning change

Gentlemen,

Please accept the following suggestion for discussion.

As a developer for a large financial institution I am

attempting to determine the feasibility of using the

functionality provided by the OpenSSL libraries in our

commercial applications. I'm sure you are already

aware that large corporations are reluctant to

implement open-sourced products due to perceived

accountability issues. This is a battle I am prepared

to take on. However, to help in this regard I'm

proposing a change of version to the next release of

OpenSSL.

To remain consistent with existing versioning schemes

I would like to see a version scheme using a

MAJOR.MINOR.BUILD whereas the next release

of OpenSSL is not v0.9.7 but v1.1.0. The main reason

for this request is due to the perceived "beta status"

of any product with a major version of zero (0). This

would help me tremendously in obtaining buy-in from

corporate management.

Finally, a MAJOR version of 1 and a MINOR version

of 1 would indicate that included in this release are

additional features (Rijndael) as well as bug fixes.

Any bug fixes to a MINOR release should have

the BUILD part incremented to reflect the latest

"stable" release of that product.

I'm hoping that you can accommodate this request

and see that it will help in publicizing the project.

I'm sure that once the version number is changed

and a press release follows that the OpenSSL

project will receive the increased interest and

attention that you all deserve. Thank you.

Reply via email to