[openssl-commits] [openssl] master update

[Richard Levitte]

The branch master has been updated
       via  6a919b44f745c1d764b6b0593b2a60bd8e342c67 (commit)
      from  79a578b90244b890c8a6a8fc26c03943da71c054 (commit)


- Log -----------------------------------------------------------------
commit 6a919b44f745c1d764b6b0593b2a60bd8e342c67
Author: Richard Levitte <levitte at openssl.org>
Date:   Sun Mar 29 09:42:58 2015 +0200

    Have a shared library version thats reasonable with our version scheme
    
    The FAQ says this:
    
        After the release of OpenSSL 1.0.0 the versioning scheme changed. Letter
        releases (e.g. 1.0.1a) can only contain bug and security fixes and no
        new features. Minor releases change the last number (e.g. 1.0.2) and
        can contain new features that retain binary compatibility. Changes to
        the middle number are considered major releases and neither source nor
        binary compatibility is guaranteed.
    
    With such a scheme (and with the thinking that it's nice if the shared
    library version stays on track with the OpenSSL version), it's rather
    futile to keep the minor release number in the shared library version.
    The deed already done with OpenSSL 1.0.x can't be changed, but with
    1.x.y, x=1 and on, 1.x as shared library version is sufficient.
    
    Reviewed-by: Kurt Roeckx <kurt at openssl.org>

-----------------------------------------------------------------------

Summary of changes:
 crypto/opensslv.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/crypto/opensslv.h b/crypto/opensslv.h
index b86665d..97c27e7 100644
--- a/crypto/opensslv.h
+++ b/crypto/opensslv.h
@@ -88,7 +88,7 @@ extern "C" {
  * should only keep the versions that are binary compatible with the current.
  */
 # define SHLIB_VERSION_HISTORY ""
-# define SHLIB_VERSION_NUMBER "1.1.0"
+# define SHLIB_VERSION_NUMBER "1.1"
 
 
 #ifdef  __cplusplus