That was my concern. Surely there must come a time when two versions of
a shared library exist (with identical major version numbers), and an
application requires to be dynamically linked to the older of the two
because of some incompatability with the newer library?
If this ever occurs, you are *required* to bump the major version
Minor version number changes are reserved for (a) bug fixes and (b)
additional interfaces that do not impact existing interfaces.