MariaDB Server Roadmap

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

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

The roadmap for MariaDB Server is formed by its engineers and product managers, with input from the community.

MariaDB Server developers work with several storage engine vendors and developers to get the best storage engines into MariaDB Server.

The collected information is then turned into specific tasks which are then prioritized and added to the roadmap in the JIRA issue tracker at jira.mariadb.org

Goals and Quality Standards

The primary goal of MariaDB Server is for it to be a practical database developed in the direction 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 Server, and to keep it stable and easy to use!

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

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

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

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

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

See Also

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.