Ensuring continuity and open collaboration

Maintenance Policy

The latest release, 10.1, was announced as stable in November 2015 and will be maintained until at least November 2020. The version currently under development, 10.2, is scheduled to be announced as stable in late 2016.

A new MariaDB server version is to be announced for General Availability at least once a year. The MariaDB Foundation guarantees that every release will be maintained for at least 5 years. The MariaDB Foundation prioritizes security fixes and major bug fixes that affect a large amount of users, and other fixes that are important to the members and sponsors of the foundation. Please become a sponsor or donor to support our work.

MariaDB general release maintenance periods

Major and Minor Version Stable (GA) Date Five year boundary date
5.1 1 Feb 2010 1 Feb 2015
5.2 10 Nov 2010 10 Nov 2015
5.3 29 Feb 2012 1 Mar 2017
5.5 11 Apr 2012 11 Apr 2017
10.0 31 Mar 2014 31 Mar 2019
10.1 23 Nov 2015 23 Nov 2020
10.2 Not Stable 5 years after stable (GA) release date

These dates constitute the public policy of the MariaDB Foundation and are not legally binding. The software is released with the GPL license as-is, without warranties.

Maintenance periods by service providers

Some MariaDB service providers might offer under contract longer, or otherwise more extensive, maintenance periods. Some Linux distributions may also offer extended support periods for the MariaDB versions they shipped.

Please contact the commercial service providers if you use MariaDB in a critical production environment and you want to have contractual warranties regarding your use and maintenance of the MariaDB software.

Semantic versioning

MariaDB aims to follow the semantic versioning standard. In client-server APIs we follow it fully and in the server we follow it in spirit.

Micro releases (patch versions) e.g. 5.5.x and 10.0.x only fix security issues and bugs. Minor version releases e.g. 5.x and 10.x add functionality but maintain backwards-compatibility. Major releases e.g. 10.0 and 11.0 may make backwards-incompatible changes.

For details about semantic versioning, see semver.org.

In all releases, including major releases, we always make sure that the mysql_upgrade facility runs correctly and the database files from any older release can be upgraded.

Sponsors

MariaDB Foundation sponsors

Tweets by @mariadb

Code statistics