We recently released a new version of XAMPP with MariaDB that did not go as planned. Although MariaDB is a drop-in replacement for MySQL, this particular release is incompatible with the version of phpMyAdmin that we were bundling. This resulted in errors like the ones described in this thread:
In that thread you will also see a new release that addresses some of those issues and that we will be making official soon. We understand how frustrating this has been for those of you that have run into this issues or that have concerns about replacing MySQL. We want to continue to make XAMPP better with every release, so this is frustrating as well for us. Two of the things that we want to improve moving forward to address this:
- Whenever possible, provide advance information when making major changes. This should give you an opportunity to provide feedback and for us give you more background on why certain changes were desirable or necessary. For example, in the particular case of MariaDB, most major Linux distributions (RedHat, Suse), cloud providers, etc. are migrating to MariaDB from MySQL for a variety of reasons, mostly related to licensing and open development. We have been delaying making the switch ourselves, but did not want to wait any longer if this is were the rest of projects and community were going.
- Provide early access to beta-testers before releasing new XAMPP versions, at least ones that provide major upgrades so we can detect these types of errors early on
There are other priorities for future XAMPP development: building and sharing a roadmap, continue to improve the documentation, Windows 64bit support, PHP 7 support, more frequent releases (at least once a month)
Please let us know which other areas you think we could improve on. I want to thank Altrea for taking the time to provide detailed feedback privately