In end of May I told about the numbering plans for the next version of MariaDB in the blog post What comes in between MariaDB now and MySQL 5.6?. We received quite a lot of feedback and criticism on the idea of calling the next version MariaDB 10.0. Here is a little more information about why it makes sense to call the next version 10.0.
This is not news for most of you. MariaDB is not just a set of patches applied on top of MySQL. MariaDB includes features which are similar to the corresponding features in MySQL, but the implementations differ, like for example the thread pool, microsecond support and query annotations in RBR binlog. Read more
We’re quite happy that we’ve released four major releases that are production ready (better known as generally available or GA in the MySQL world) in the last 26 months. That is just a little over two years, and a whole lot of features. In that same time, MySQL has seen one GA release (MySQL 5.5) and we’re all eagerly awaiting the upcoming MySQL 5.6.
You’ll note that we built MariaDB 5.1, 5.2, and 5.3 based on the MySQL 5.1 codebase. A significant number of features went into MariaDB 5.3 (our biggest GA release to date), with the biggest changes in the optimizer in over a decade. Read more
On Friday last week, after the intensive days of the conference, Ars Technica wrote and published a nice article about MariaDB including many of the messages we had been delivering during the conference, http://arstechnica.com/business/news/2012/04/mysql-founders-latest-mariadb-release-takes-enterprise-features-open-source.ars.
Last year, when it became clear that O’Reilly wasn’t going to arrange the MySQL user conference in the future, there was a lot of discussion on who should arrange it. In the end Percona was pretty fast informing everyone that they had booked the convention center in Santa Clara to arrange the conference this year. Read more
We are pleased to announce the immediate availability of MariaDB 5.3.6. This stable (GA) release incorporates MySQL 5.1.62, some performance improvements, and several bug fixes.
Most importantly, MariaDB 5.3.6 includes a fix for a bug which, under certain rare circumstances, allowed a user to connect with an invalid password. This is a serious security issue. We recommend upgrading from older versions as soon as possible.
Most importantly, MariaDB 5.1.62 and 5.2.12 include a fix for a bug that under certain rare circumstances allowed a user to connect with an invalid password. This is a serious security issue. We recommend upgrading from older versions as soon as possible.
Update: MariaDB 5.1.62 and 5.2.12 have been released. They contain an important security fix.
We are pleased to announce the immediate availability of MariaDB 5.5.22-rc. MariaDB 5.5.22 is the first release candidate (RC) release in the 5.5 series and follows the MariaDB 5.5.20-alpha and 5.5.21-beta releases. We hope to follow it up soon with a Stable (GA) 5.5 release.
We are pleased to announce the immediate availability of MariaDB 5.5.21-beta. MariaDB 5.5.21 is the first Beta release in the 5.5 series and follows the initial MariaDB 5.5.20-alpha release. We hope to follow it up soon with Release Candiate and then Stable (GA) 5.5 releases.
MariaDB 5.5.21 beta is a merge of MariaDB 5.3 and MySQL 5.5 with some limited additional bug fixes. In this release we have added some extra notable features including an improved thread pool, an updated SphinxSE storage engine for fulltext search, and the ability to selectively skip replication of binlog events. Extra features planned for MariaDB 5.5 will be pushed into subsequent releases. Read more