I noted earlier today in Refining MySQL Community Server
that it would be
just a matter of time and someone will start building RPM/Debian packages from the source repository.
I clearly didn't have my first cup of coffe yet when writing that as off course I forgot we already have DorsalSource
So I do not quite get it. Where is the technical difference between the Enterprise and the Community Server of MySQL now that MySQL AB has effectively back paddled from their commitment made with the initial split? If the Community Server now does not get new shiny features and be stable like the Enterprise Server, where is the difference? Jeremy is asking the same question. Where is the new test bed for community contributions?
It all seems to boil down to either there is none and MySQL AB has effectively gone back to status quo, leaving the Enterprise server as a way to make their paying customers feel like they are getting …
[Read more]With the my blog entry yesterday on Refining MySQL Community Server, did anything really change? If so, was it for the better or for worse for the community?
My answer is “not much”, and “for the better”, but feel free to disagree.
Judging from some reactions in the community, a lot changed, and for the worse.
I've just read post http://www.planetmysql.org/kaj/?p=123 about MySQL
plans of including community contributions into releases. I
understand MySQL's interest to make releases stable, and includes
contributions only into development tree, but this is not
something I would like to see.
Look, MySQL 5.0 was shipped as production on 19 October 2005.
Since almost 2 years there is no 5.1 GA, it is still on road.
That means if we push our changes into development tree 5.2, the
our contrinution will be released in 2 years. Actually this fact
make me absolutelly not interested in contrubution my skills into
improving MySQL.
One more thing I think about - the difference between between Enterprise and Community releases in 5.0 is only SHOW PROFILE patch, the same probably will be in 5.1. I just wonder how the single patch makes difference, so there is a need to make two …
[Read more]Yesterday Kaj Published changes to MySQL Community Release Policies. I knew about them a bit in advance but now they are public I can comment a bit.
In general I'm disappointed and think this is moving in the wrong direction, it also makes me to think hard if MySQL is out of more creative solutions to increase the sales revenue ?
The main issue for me is Change policy for MySQL Community version. We are patching MySQL with minor extension so this concerns us a lot - it would be much easier to make our customers to run Community version (at least temporary) compared compiling patched version for them. There was as hope MySQL Community version would allow to quickly make changes available but not it is gone.
Honestly I do not think it ever work. We have submitted our patches for microsecond resolution of slow queries over half a year ago. These patches had a …
[Read more]A few days ago, I got the opportunity to hear about some upcoming changes in MySQL Community and MySQL Enterprise. I’ve been waiting for an official announcement before commenting on the changes, and Kaj has finally posted the official announcement on his blog in Refining MySQL Community Server.
In summary, the changes are:
Different things can be said about Kaj Arno's , Refining MySQL Community Server but given the fact that the source will continue to be freely available from Bitkeeper I see no issues apart from a possible growth in real community MySQL with real contributions.
In Mike Kruckenberg's article on the topic someone comments and asks how this is different from the RedHat model, I only see one difference, today we don't have a CentOS yet for MySQL .. I`m sure it's just a matter of time and someone will start building RPM/Debian packages from the source repository. (If it's not already happening today)
As long as MySQL keeps all their source code free ..
Different things can be said about
Kaj Arno's , Refining MySQL Community Server but
given the fact that the source will continue to be freely
available from Bitkeeper I see no issues apart from a possible
growth in real community MySQL with real contributions.
In Mike Kruckenberg's article on the topic someone comments and asks how this is different from the RedHat model, I only see one difference, today we don't have a CentOS yet for MySQL .. I`m sure it's just a matter of time and someone will start building RPM/Debian packages from the source repository. (If it's not already happening today)
As long as MySQL keeps all their source code free ..
Oracle contributes code to Linux community. Linux Foundation adds legal talent. Luxoft open sources test automation tool. (and more)
Oracle Contributes Enhancements To Linux Community, Oracle (Press Release)
Leading Open Source Legal Experts Join Linux Foundation, Linux Foundation (Press Release)
Outsourcing Leader Luxoft Contributes New Test Automation Tool to Open Source, Luxoft (Press Release)
Oracle Provides Six New Validated Configurations for Linux …
[Read more]
Direct play this episode at:
http://technocation.org/content/oursql-episode-21%3A-rise-mysql-dba-1
Paul Vallee is back for this non-technical podcast about the special creature that is the MySQL DBA.
News:
October 2006 Enterprise/Community Split announcement
http://www.planetmysql.org/entry.php?id=4393
Current clarification of Enterprise/Community split
http://www.planetmysql.org/kaj/?p=123
Dorsal Source, a community-focused website whose goal is to
provide builds of MySQL and related products.
http://www.dorsalsource.org
Learning Resource:
MySQL Camp II, August …