[something happened to this post and I am reposting it]
It was suggested by Monty that the posts I've made about MariaDB are for publicity. This simply isn't true. I would have much preferred a different outcome in my interactions with MariaDB. I figured that they would end up giving me a hard time, and I'd be stubborn and we'd both hate each other for as long as I could keep from leaving. A quick separation actually seems much better in such context. Regardless, I would have preferred to speak amicably to the MariaDB Corporation about switching the license back, or at least moving to the new license at the time of the notification of the community, ie, changing the license so that bug fixes for 1.3.4 were not mingled with new 2.0 features.

It could have been easily possible to have a 1.3.5 release that fixes the major bugs in 1.3 and then release a new set of features as 2.0. This would have been at least reasonable, but by …

OPEN SOURCE IS ABOUT BEING OPEN NOT JUST ABOUT SOURCE CODE.
MariaDB makes changes to the storage engine API without even consulting the mailing list. In fact, some MariaDB replication features don't work with TokuDB because a new storage engine API call is required, and this call requires functionality that might not exist in all engines, that is, the engine must be able to convert a transaction id into a THD object. No API is provided by the SE to make this translation. MariaDB must communicate changes to the storage API to the public so that the public can ensure that tools made to work with MariaDB continue to work with MariaDB. It doesn't matter that TokuDB is made by a competitor. In a foreign language article, Kaj recently said MariaDB is more open than Oracle because it includes many storage engines. This is a crappy argument. MariaDB is trying to say they are better than Oracle because they profit more from including code they didn't …

MariaDB 10.0.17 was recently released, and is available for download here:

https://downloads.mariadb.org/mariadb/10.0.17/

This is the eighth GA release of MariaDB 10.0, and 18th overall release of MariaDB 10.0.

For the most part, there are not a whole lot of new changes to report for this release, but there is a new version of the Audit Plugin and many other engines have been updated as well.

Here are the main items of note:

1. The new version of the Audit Plugin is 1.2 is included with the following new features:
   • In the audit log passwords are now masked, i.e. the password characters are replaced with asterisks.
   • It’s now possible to filter logging to include only DDL (CREATE, ALTER, etc.) or DML (INSERT, UPDATE, etc.) statements.
   • For more information …

MariaDB 10.0.16 was recently released (~1.5 months ago on 1/27/2015 – sorry for the delay on my end – I was just extra busy in my spare time recently), and is available for download here:

https://downloads.mariadb.org/mariadb/10.0.16/

This is the seventh GA release of MariaDB 10.0, and 17th overall release of MariaDB 10.0.

For the most part, there are not a whole lot of changes to report for this release, but there are 2 enhancements of note – one being the JSON table type (still *experimental*) and the other a new variable to aid with index statistics calculations on large tables, as well as some security fixes.

Here are the main items of note:

1. Updates to the CONNECT handler (supporting the …

MariaDB 10.0.15 was recently released, and is available for download here:

https://downloads.mariadb.org/mariadb/10.0.15/

This is the sixth GA release of MariaDB 10.0, and 16th overall release of MariaDB 10.0.

This release has an important InnoDB/XtraDB fix, a new addition, security enhancements (and improvement) – all related to yaSSL, so be sure to check out these fixes if you’re running MariaDB 10.0, and not up to 10.0.15 yet. (MariaDB 10.0 is the current stable series of MariaDB. It is an evolution of the MariaDB 5.5 with several entirely new features not found anywhere else and with backported and reimplemented features from MySQL 5.6.)

Here are the main items of note:

1. This release fixes a serious bug in InnoDB and XtraDB that sometimes could cause a hard lock up of the server ( …

In January I wrote my first post about node.js and MariaDB . In February I continued with a second post about using jQuery and some GIS calculations. Now it is time for the third and this time the main focus is not so much on GIS functionality, but instead on the capabilities MariaDB has for handling piles of unstructured data. In this case I’ll be focusing on crunching a pile of XML files without importing the XML data itself.

MariaDB 10.0, which had its GA launch in early April, includes the Connect engine. It has been developed to dynamically access all …

We announced yesterday that the call for proposals for MySQL Connect @ OpenWorld 2014 is now open!

Part of Oracle OpenWorld 2014, MySQL Connect @ OpenWorld will be held September 29 - October 2 in San Francisco.

We encourage MySQL customers, partners and community members to submit proposals to present best practices, case studies and insights you’ve gained working with MySQL. Proposals can be submitted for conference sessions, Birds-of-a-Feather sessions and tutorials.

MySQL Connect @ OpenWorld will feature five tracks:

• Performance and Scalability
• High Availability and Replication
• Cloud and Big Data
• Database Administration and DevOps
• Architecture and Application …

In January we encouraged you to prepare for the MySQL Connect Call for Papers, indicating how.

While dates are still subject to change, we wanted to let you know that the CFP (for MySQL Connect and Oracle OpenWorld overall) will likely open around March 18th. Remember to prepare your submissions in advance in order to swiftly submit them during the 4 to 5 weeks that the CFP will remain open!

As announced last month, MySQL Connect will this year be aligned with Oracle OpenWorld and run from Monday September 29 to Thursday October 2, 2014, in San Francisco.

The MySQL Connect and Oracle OpenWorld Calls for Papers will also open at the same time, and you will most likely be able to submit your sessions between March 4 and April 8 (dates subject to change).

While you will have 5 weeks or so to actually submit your talk proposals, you can already prepare your submissions NOW in order to be ready to submit then, and here is the key information you need to do so. In order to submit a session, you will need to provide:

• Title
• Conference session type: This can be either a conference session (1 hour), a Birds-of-a-Feather session (1 hour), or a tutorial (2,5 hours). You are …

We're very pleased to announce that MySQL Connect will next year take place from Monday September 29 to Thursday October 2, 2014, in San Francisco. And there will be a welcome reception on Sunday September 28 evening.

During the past 2 years we’ve run MySQL Connect during the weekend prior to Oracle OpenWorld, and we repeatedly got feedback that avoiding the weekend would be better. Well, this is now done! MySQL Connect will be fully aligned with Oracle OpenWorld. This will also enable us to have more room to schedule sessions across the 4 days and to be better integrated within Oracle OpenWorld overall, which was also part of the feedback we’ve got.

We will provide more details down the road but wanted to make sure you could save the dates and make your plans accordingly.

The Call for Papers will likely open in March, so start thinking about your topics now in order to submit them swiftly when it …