MariaDB Roadmap

You are viewing an old version of this article. View the current version here.

This page talks in general about the MariaDB roadmap, and how it is formed.
The roadmap it describes is located in our JIRA issue tracker:

The roadmap of MariaDB is formed by the community on the maria-developers list on Launchpad, at conferences and developers events, and in discussions with customers of MariaDB Foundation members, like the MariaDB Corporation, who are part of developing MariaDB.

The MariaDB developers are also working with several storage engine vendors and developers to get the best storage engines into MariaDB.

The collected information is then turned into specific tasks which are then prioritized and added to the roadmap in the MariaDB JIRA issue tracker:

Goals and Quality Standards

The primary goal of MariaDB is for it to be a practical database developed in the direction MariaDB users and developers want it to be developed. Each feature should ideally be developed by or for users who want to test and put the feature into production ASAP this helps ensure we don't implement features no one wants or needs.

We are also putting a lot of effort into speeding up MariaDB, and to keep it stable and easy to use!

The MariaDB source tree is maintained by the MariaDB developers. They are the primary contributors to the MariaDB project and the ones who are ultimately responsible for the quality of the code.

MariaDB 5.1, MariaDB 5.2, and MariaDB 5.3 were built off of MySQL 5.1.

MariaDB 5.5 was a combination of MariaDB 5.3 and MySQL 5.5.

MariaDB 10.0, and later build off of the previous MariaDB release with backported features from MySQL and entirely new features not found anywhere else.

Short descriptions of the various MariaDB releases and their main new features can be found on the MariaDB Releases page.

See Also


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.