|
|
|
|
|
If you missed Kaj's announcement in the splashing news commotion at the latest MySQL Conference, then you may be interested to get this information again. There was a piece of news that should be extremely important for all the users. MySQL server binaries used to be split between Enterprise and Community, and they were released with separate schedules. Not anymore. Starting from April 2009, the MySQL Community and Enterprise editions are built from the same code, and they are released with the same frequency. |
There were rumors about the two editions being treated differently. Since we are talking about it, let me assure you that this is not the case. Both editions go through the same tests, and even more so now, since they come from the same tree. Until version 5.0.81, there was a separate tree for Community (with extra features), but now there is only one.
For every bug fix release, both editions are released on the same day.
Another difference that has disappeared is the version number. Previously, even numbers were for Enterprise, odd ones for Community. Now, every version number identifies both the Community and Enterprise edition.
Enjoy the best bits from MySQL. download at will!
So, why build something called "community" and something called "enterprise" then, can it just be "MySQL" again?
Or is that the intent, at a later stage?
Would make sense, I think.
Anyway, good stuff!
Posted by Arjen Lentz on July 21, 2009 at 06:04 PM PDT #
What's different about an Enterprise Quarterly Service Pack (QSP) binary? See:
http://dev.mysql.com/doc/refman/5.1/en/news-5-1-34sp1.html
It looks like 5.1.34 + some changes. If Enterprise and Community binaries are the same, why is there an Enterprise QSP?
Posted by Tom Hotchkiss on July 23, 2009 at 09:21 AM PDT #
The QSP is not a new release, but a consolidation of previous releases that is offered to paying customers only.
Notice the release dates.
Posted by Giuseppe Maxia on July 23, 2009 at 10:16 AM PDT #