Last week in Prague, I met with Mark Shuttleworth of Canonical at the Ubuntu Developer Summit for version 8.10.

myself, Mark Shuttleworth, Arseniy Kuznetsov (Sun, NetBeans), Matt Zimmermann (Canonical CTO)

As you would expect, we discussed Canonical’s and MySQL’s offerings to the market. And we pondered on possibilities for joint customers to have the best of both worlds: Wouldn’t it be great if MySQL users on Ubuntu could get the “best bits” from MySQL through the software delivery mechanisms of Ubuntu?

Mark drew the above picture on a piece of paper (which I used Omni Graffle to capture in .png form), and we decided to explore how the “curved orange” part of the customer experience could be improved.

The upcoming 5.1.25 release will see a change with regards to MySQL Cluster:

MySQL 5.1.25 binaries will be released without Cluster support.

This is due to a change in the development cycle of MySQL Cluster. The work on Cluster specific features is largely independent from the rest of the MySQL Server, which has resulted in our decision to release MySQL Cluster separately from the rest of the MySQL Server, effective with MySQL 5.1.25.

This change just goes for the binaries, though. Let me reassure you that:

• Sun is still releasing MySQL Cluster under the GPL, as before.
• MySQL 5.1 source code will still include Cluster, and you can download and compile it with Cluster, if you wish.

The only change is that we’re now releasing two separate packages.

MySQL Cluster is being developed and maintained at a different pace, compared to the regular server. In addition, we have learned that our current users of MySQL Cluster are not as concerned about the regular server’s features. Typical Cluster customer installations rely mostly on updated cluster features. Many users of Cluster use the direct API rather than the SQL interface.

We hope this division will bring benefits for all parties involved:

• Cluster releases will be happening more quickly, as Cluster releases are fairly independent of MySQL Server releases. With new releases of MySQL Cluster no longer tied to the release of the regular server, cluster users will get their updates as soon as the Cluster software is updated, regardless of whether the regular server is being patched or not.
• The new Cluster package includes the Carrier Grade Edition, which contains a juicy list of features (http://dev.mysql.com/doc/refman/5.1/en/mysql-cluster-changes-5-1-ndb-6-2.html).
• Users of the main MySQL Server will now be able to download a smaller package with a quicker test suite. This should really help those with low bandwidth connections.

The change is evident when you look at the developer zone (http://dev.mysql.com) where MySQL Cluster uses a different release numbering scheme from MySQL Server, and is labeled 6.2.15. This is not the regular server version. 6.2.15 is the Cluster version, and this package is based on MySQL 5.1.

Bug fixes to the Cluster will be ported to the main server when appropriate. Bug fixes to the main server will be merged to the Cluster sources on a regular basis.

Finally, where shall you turn for the downloads?

• If you need MySQL binaries with Cluster enabled, there is a specific downloads page http://dev.mysql.com/downloads/#mysql-cluster
• MySQL Server (slimmer now, without the NDB binaries), is available as always at http://dev.mysql.com/downloads/

As reported yesterday from CommunityOne:

• MySQL Server is and will always remain fully functional and open source,
• so will the MySQL Connectors, and
• so will the main storage engines we ship.

In addition:

• MySQL 6.0’s pending backup functionality will be open source,
• the MyISAM driver for MySQL Backup will be open source, and
• the encryption and compression backup features will be open source,

where the last item is a change of direction from what we were considering before.

The change comes from MySQL now being part of Sun Microsystems. Our initial plans were made for a company considering an IPO, but made less sense in the context of Sun, a large company with a whole family of complementary open source software and hardware products.

I’d like to shed some light on the big picture, in two different ways — openness, and the business model.

MySQL’s openness manifests itself in three ways:

• MySQL’s code is open.
• MySQL’s APIs are open.
• MySQL’s data formats are open.

These form a foundation around the MySQL Server and its connectors on which we (Sun), our partners, and the community can all freely build upon. And through this openness, we will always provide a means for our users to easily export their data from MySQL.

Then for MySQL’s business model. To financially support MySQL’s free and open source platform, we have a business model which allows both community and commercial add-ons, and we remain committed to it. We believe the model to be useful for both those who spend money to save time, and those who spend time to save money.

As Mårten mentioned yesterday in the CommunityOne panel, expect Sun/MySQL to continue experimenting with the business model, and with what’s offered for the community and what’s offered commercial-only. We won’t always know the right answer from the beginning, but we want MySQL to be the most popular database for both paying and non-paying users.