One thing that people seem to forget with regards to MariaDB is that switching over to it might break paid application support since MariaDB is not listed in the relevant application supported platform like for example.
No they don't forget about it:
Going through the thread I currently see two reasons to keep packaging mysql after switching to mariadb:
Firstly, some admins may be bound to mysql because of the certification or similar reason, but it probably won't be a technical reason. It'd be nice if admins work with providers in such cases and push them to add mariadb into set of "supported" options. I believe there won't be technical barrier to do so, so everyone could benefit from that.
Second, if mariadb differs more in the future and stops to be "drop-in" replacement, then we'll need an alternative for applications, where mariadb won't be suitable enough. Nevertheless, this is not a current issue right now.
In both cases we'll probably need some time to evaluate how the things with mariadb goes, so I'd suggest to wait, observe, test and after some time to re-open the discussion and make a decision about dropping mysql.
This is sensible approach: if MariaDB is a default in most Linux distributions and it's not a disaster (WRT security, stability, etc) then "paid support" will eventually will be offered for it and if MySQL is available as [non-default] alternative then everything will be fine till it happens.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds