From 319cda6ab5796f22b3bda871eb6bedb784ab55d8 Mon Sep 17 00:00:00 2001 From: Teemu Murtola Date: Sat, 4 Jul 2015 06:48:44 +0300 Subject: [PATCH] Bump various version numbers It is unclear what will the next version be numbered, but bumped the version numbers nonetheless to make the distinction between master and release-5-1 clear. Change-Id: I1cfe9f2a2523056f20cc825025425fc9429c89b6 --- cmake/gmxVersionInfo.cmake | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/cmake/gmxVersionInfo.cmake b/cmake/gmxVersionInfo.cmake index 61e595aa31..162b32818e 100644 --- a/cmake/gmxVersionInfo.cmake +++ b/cmake/gmxVersionInfo.cmake @@ -211,13 +211,13 @@ endif() # The GROMACS convention is that these are the version number of the next # release that is going to be made from this branch. set(GMX_VERSION_MAJOR 5) -set(GMX_VERSION_MINOR 1) +set(GMX_VERSION_MINOR 2) set(GMX_VERSION_PATCH 0) # The suffix, on the other hand, is used mainly for betas and release # candidates, where it signifies the most recent such release from # this branch; it will be empty before the first such release, as well # as after the final release is out. -set(GMX_VERSION_SUFFIX "-beta1") +set(GMX_VERSION_SUFFIX "") # Conventionally with libtool, any ABI change must change the major # version number, the minor version number should change if it's just @@ -228,7 +228,7 @@ set(GMX_VERSION_SUFFIX "-beta1") # here. The important thing is to minimize the chance of third-party # code being able to dynamically link with a version of libgromacs # that might not work. -set(LIBRARY_SOVERSION_MAJOR 1) +set(LIBRARY_SOVERSION_MAJOR 2) set(LIBRARY_SOVERSION_MINOR 0) set(LIBRARY_VERSION ${LIBRARY_SOVERSION_MAJOR}.${LIBRARY_SOVERSION_MINOR}.0) -- 2.22.0