Comments - Why two versions (10.0 and 10.1)?
Content reproduced on this site is the property of its respective owners,
and this content is not reviewed in advance by MariaDB. The views, information and opinions
expressed by this content do not necessarily represent those of MariaDB or any other party.
Hi Elliot,
I would like to add on top of Daniel answer:
- Increasing major release cycle period, is giving MariaDB captains and external contributors closer windows of time for modifying system objects that are needed by a new feature. That's a trade off between accepting more code changes vs the time users spend in upgrading. In any open source project your time is an important contribution to the product by exposing new code to a wider community.
- Regarding the upgrade procedure, captains are always fixing bugs regarding compatibility issues with older versions of system tables, engine formats and protocols, but in some cases new or existing features can be broken if the code don't found the expected version of protocols and objects. I can quote a case where the performance was really impacted on VIEWS keeping the older version of the object.
You can still skip the upgrade at your own risk, the best advice in this case is good tracking of the error log. Compatibility issues should be trigger in this log if they are required or advised.
As binary compatibility can't be 100% guaranty it's always suggest to apply the mysql_upgrade process and reloading your data from a dump. We don't give up on keeping that process more simple, 10.1 have an interesting feature that can make this it more easy in the future see https://mariadb.atlassian.net/browse/MDEV-4262