The Ultimate Guide to High Availability with MariaDB

MariaDB Feature Deprecation Policy

It is unacceptable for a user to upgrade from a supported version A where a feature works normally to a version B where a feature doesn't exist without a warning.

Thus, when a feature is removed for some reason, the sequence of steps is as follows:

  1. the feature is marked as deprecated.
  2. we wait until all releases where the feature is not deprecated have reached EOL
  3. now the feature can be removed

With an LTS lifetime of 5 years, step 2 normally means that a feature cannot be removed until it's marked deprecated for 5 years. After that it can be removed or hidden behind a dedicated old-mode option, which will give it at least 5 more years until disappearance.

Comments

Comments loading...
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.