MySQL 6.2 is GA, but 5.1 is RC and 6.0 is alphaFri, May 23, 2008 in Commentary Databases
MySQL's version numbering is getting harder and harder to understand. In fact, it's getting surreal.
Let me state up front that there's probably a lot I don't know here. But if I don't know, how on earth can the general public figure it out?
Before we begin, let's define terms: GA is completely done, ready for use. RC is a release candidate: don't change anything, just fix bugs because we're charging towards a release here. Beta is possibly unsafe code, use at your own risk. Alpha is known to have significant bugs, but if you're curious please play with it.
Now for the releases/versions game. Let's recap:
- 5.0 has version numbers that leapfrog each other in features and functionality. SHOW PROFILES -- now you see it, now you don't.
- 5.1 has been "... released to general availability [as] a near-final release candidate," whatever that means.
- 5.1 has just had drastic changes in the RC stage. (Remove Federated in 5.1.24, remove RENAME DATABASE, remove Cluster.) And it's going to have more changes before it's released, too: Federated will be added back in 5.1.25.
- 5.2 doesn't exist. Last year at the MySQL conference, someone made an abrupt decision to skip 5.2 and inflate the version numbers to 6.0, which has big changes in the query optimizer and other areas.
- 6.0 is alpha, but it includes Falcon, which is beta even though Falcon has extremely bad bugs that its developers claim are not bugs.
- 6.1 doesn't exist as far as I know.
- 6.2 not only exists, but it is GA. Not only that, but it just... appeared as GA, as far as I know. No RC stage, no nothing -- at least, nothing on the MySQL website that I see (certainly no manual version). It went from nonexistent to GA instantaneously as far as I know. It was created by extracting the Cluster code from 5.1.
- 6.2 is GA, but 5.1 is RC.
- 6.2 is GA, but 6.1 doesn't exist as far as I know.
- 6.2 is GA, but 6.0 is alpha. (Hopefully you see the pattern here.)
- 6.2 is GA, but presumably does not include the changes made in 6.0, since it was derived from 5.1′s code.
What is going on here?
How is this an improved release model? What is improved about this?
How in the world can anyone figure out what versions of the software have what features? Who can make an educated decision about what product to use in this situation? Are people supposed to just rely on the sales people to help them figure out what to use? Boy, is that trusting the fox to guard the henhouse.
Why didn't they just release 5.1 Cluster as GA separately, if that reflected the reality in the code? They certainly missed an opportunity to show some progress on 5.1. As it is, 5.1 got robbed of its chance to have at least some of its code go GA after more than 2.5 years in development. Now 5.1 looks like even more of an embarrassment -- hey 5.1 team, how come you can't get anything out the door when these 6.2 people are releasing GA products? Not to mention 6.0 -- you guys look bad now too! (Just kidding.)
I tried to draw a timeline of MySQL's release history, in some detail in the 5.0 history and in very basic detail in the 5.1 and 6.0 and 6.2 trees. You can take a look at that. It's worth studying for 5 minutes or so, even though it's kind of ugly. There are lots of oddities to notice about it. Enjoy:
About The Author
Baron is the founder and CEO of VividCortex. He is the author of High Performance MySQL and many open-source tools for performance analysis, monitoring, and system administration. Baron contributes to various database communities such as Oracle, PostgreSQL, Redis and MongoDB.