Following the discussion that we had on the previous documents and on all the input I got, I created a new version (v3.0-dev) for this proposal:
https://docs.google.com/document/d/1p6l7VYn176JKzOtERdp9OG0HcyhnJZnVdRLD07L_1wE/ It's written from the point of view that the comment in opensslv.h and the documentation in OPENSSL_VERSION_NUMBER.pod are correct as to what the components in the version number are, and that we simply didn't do as the docs said since 1.0.0. So the idea is to simply reset, and then synthesize the value of existing macros (especially OPENSSL_VERSION_NUMBER) to be safe to use as we have observed that users do. This document leaves a few questions open: 1. what version will the next major release actually be? 2.0.0 has been suggested, and 3.0.0 as well. I see that as out of scope for this document, and should simply be voted on by the OMC at some point. 2. how should we handle ABI compatibility / incompatibility? It's possible that it's out of scope here, I'm unsure... 3. policies on what should and should not go into what version number level? I see that as out of scope for this document, but is definitly a related topic to discuss. Cheers, Richard -- Richard Levitte levi...@openssl.org OpenSSL Project http://www.openssl.org/~levitte/ _______________________________________________ openssl-project mailing list openssl-project@openssl.org https://mta.openssl.org/mailman/listinfo/openssl-project