I notice the maxscale rpms have names such as:

• maxscale-1.2.0-x86_64-rhel6.rpm

You can see the actual version and rpm release number by doing this:

$ rpm -qip maxscale-1.2.0-x86_64-rhel6.rpm
warning: maxscale-1.2.0-x86_64-rhel6.rpm: Header V4 RSA/SHA1 Signature, key ID 8167ee24: NOKEY
Name : maxscale Relocations: /usr
Version : 1.2.0 Vendor: MariaDB Corporation Ab
Release : 1 Build Date: Thu 16 Jul 2015 06:41:00 PM CEST
Install Date: (not installed) Build Host: ip-10-208-38-145.eu-west-1.compute.internal
Group : unknown Source RPM: maxscale-1.2.0-1.src.rpm
Size : 15751852 License: GPLv2
Signature : RSA/SHA1, Thu 16 Jul 2015 06:48:48 PM CEST, Key ID 70e4618a8167ee24
Summary : MaxScale
Description :
The MariaDB Corporation MaxScale is an intelligent proxy that allows forwarding of
database statements to one or more database servers using complex rules,
a semantic understanding of the database statements and the roles of
the various servers within the backend cluster of databases.

MaxScale is designed to provide load balancing and high availability
functionality transparently to the applications. In addition it provides
a highly scalable and flexible architecture, with plugin components to
support different protocols and routing decisions.
$

So normally it would be good to see the package name as: maxscale-1.2.0-1.x86_64-rhel6.rpm or similar. If the packaging gets updated but the actual maxscale code does not change then you'd generate a new rpm: maxscale-1.2.0-2.x86_64-rhel6.rpm and something like that might be nice for MXS-302. Otherwise it's impossible to distinguish different rpms etc.

Note: both MariaDB and MaxScale have "odd" rpm file names which is rather confusing. It's much easier if they follow the typical <name><version><release>.<arch>.rpm type structure which everyone else uses.