Certain components of a server release have separate version numbers. This confuses users because it's generally not clear what component version corresponds to what server version. Currently it is solved by long tables in KB, for example,

• https://mariadb.com/kb/en/connect/
• https://mariadb.com/kb/en/about-mariadb-connector-c/#mariadb-connectorc-releases-included-with-mariadb-server-releases

This is inconvenient.

To make it easier to use we can embed the component version into a package version. That is, for example, Connect 1.07.0001 in MariaDB 10.4.12 could be in an RPM package MariaDB-connect-engine-10.4.12-1.07.0001-1.distro.arch.rpm, this will make it immediately clear what connect version the user is installing.

This current task is about extending the build framework to support such combined package versions. It will not change package versions of Connect or Connector/C.

technically this approach would make it possible to "intermediate" package versions, for example, after releasing MariaDB-connect-engine-10.4.12-1.07.0001, it would allow releasing MariaDB-connect-engine-10.4.12-1.07.0002 without re-releasing all other packages. But such an intermediate release would imply a new source rpm (or deb) package and what version will it have? It cannot be 10.4.12, that is already taken