VERSION: Update .so versions for v2.1.0 release

Set all "c:r:a" values to 30:0:10.  Rationale:

- Recall that v2.0.0 was released with c:r:a values of 20:0:0.
  - The v2.0.x series currently mostly has 20:r:0 values (but a few
    21:r:1 and 22:r:2 values).
- Setting c=30 for v2.1.0 means that the v2.0.x series (which is still
  active) still has plenty runway ahead of it in case it needs to update
  the c values of its libraries.
- Additionally, this sets a precedent that each new release series of
  Open MPI should increment its c value by 10 (to give plenty of
  "room" in the c space for the prior release series).  For example:
  - At this point in time, a v2.2.x series is not planned.
  - The next release series will be v3.0.0.
  - The v3.0.0 series' c value should therefore be 40.
  - However, if we later decide to release a v2.2.x series, its c
    values will be bound by the v2.1.x series (which started with
    c=30) and the v3.0.x series (which will start with c=40).  There's
    plenty of room in the c space for a v2.2.x series (e.g., it might
    be able to start with c=35).
  - In short: increasing c by 10 for new release series is meant to
    give plenty of space for unanticipated future release actions.
- Setting a=10 for v2.1.0 means that the shared libraries in this
  release will be backwards compatible with the v2.0.x series.
- 30:0:10 for *all* shared libraries may be overkill, because -- by
  definition -- we only care about ABI compatibility with the MPI and
  OpenSHMEM APIs.  Meaning: setting 30:0:10 for the ORTE, OPAL, and
  common libraries may not be completely necessary.  The main reason
  for setting the ORTE/OPAL/common libraries to these values is to
  ensure that we do not run into .so version overlap during the rest
  of the v2.0.x and v2.1.x series.

Signed-off-by: Jeff Squyres <[email protected]>

Author: jsquyres

VERSION

@@ -82,17 +82,18 @@ date="Unreleased developer copy"
 # Version numbers are described in the Libtool current:revision:age
 # format.
 
-libmpi_so_version=20:1:0
-libmpi_cxx_so_version=20:0:0
-libmpi_mpifh_so_version=20:0:0
-libmpi_usempi_tkr_so_version=20:0:0
-libmpi_usempi_ignore_tkr_so_version=20:0:0
-libmpi_usempif08_so_version=20:0:0
-libopen_rte_so_version=20:0:0
-libopen_pal_so_version=21:0:1
-libmpi_java_so_version=20:1:0
-liboshmem_so_version=20:1:0
-libompitrace_so_version=20:0:0
+libmpi_so_version=30:0:10
+libmpi_cxx_so_version=30:0:10
+libmpi_mpifh_so_version=30:0:10
+libmpi_usempi_tkr_so_version=30:0:10
+libmpi_usempi_ignore_tkr_so_version=30:0:10
+libmpi_usempif08_so_version=30:0:10
+
+libopen_rte_so_version=30:0:10
+libopen_pal_so_version=30:0:10
+libmpi_java_so_version=30:0:10
+liboshmem_so_version=30:0:10
+libompitrace_so_version=30:0:10
 
 # "Common" components install standalone libraries that are run-time
 # linked by one or more components.  So they need to be versioned as
@@ -102,11 +103,11 @@ libompitrace_so_version=20:0:0
 # OMPI layer
 
 # ORTE layer
-libmca_orte_common_alps_so_version=20:0:0
+libmca_orte_common_alps_so_version=30:0:10
 
 # OPAL layer
-libmca_opal_common_cuda_so_version=20:0:0
-libmca_opal_common_libfabric_so_version=20:0:0
-libmca_opal_common_sm_so_version=20:0:0
-libmca_opal_common_ugni_so_version=20:1:0
-libmca_opal_common_verbs_so_version=20:0:0
+libmca_opal_common_cuda_so_version=30:0:10
+libmca_opal_common_libfabric_so_version=30:0:10
+libmca_opal_common_sm_so_version=30:0:10
+libmca_opal_common_ugni_so_version=30:0:10
+libmca_opal_common_verbs_so_version=30:0:10