Sergei,<br><br>I just wanted to mention product version and how it is encoded in RPM and DEB packages are 2 different things. <br><br>We have similar problem with Percona Server, adding some unstable features and we plan to either solve it by prefix or different repository.<br>
<br>Inventing  your own MariaDB 5.2 is very confusing, seriously <br><br>Are fixes in MySQL 5.1.47 in MariaDB 5.2.0  ?       Requirement to go and check the docs all the time is inconvenient.<br><br>May be some time in the future amount of changes becomes so large the base MySQL version will not be relevant any more but it will take time.<br>
<br><br><br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
We cannot just make up any numbering scheme we want - it must fit into<br>
what distributions and various package managers expect from a version<br>
number.<br>
<br>
And as far as I understand, the usual expectations are - three numbers<br>
as a version, an optional suffix, and a local (distribution specific)<br>
revision number.<br>
<br>
I&#39;m not sure the sufix is always significant, that is, I don&#39;t know how<br>
they treat two releases that have exactly the same version number, but<br>
different suffixes. In MySQL the suffix (-alpha, -beta) was  not<br>
significant, and I don&#39;t remember if there was a reason for it or not.<br>
<br>
Regards,<br>
<font color="#888888">Sergei<br>
</font></blockquote></div><br><br clear="all"><br>-- <br>Peter Zaitsev, CEO, Percona Inc.<br>Tel: +1 888 401 3401 ext 501   Skype:  peter_zaitsev<br>24/7 Emergency Line +1 888 401 3401 ext 911<br><br>Percona Training Workshops <br>
<a href="http://www.percona.com/training/">http://www.percona.com/training/</a><br>