<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.6.5" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: &#8220;It&#8217;s Not Dead, It&#8217;s Just Resting!&#8221; a.k.a., MySQL, Ethics and Death</title>
	<link>http://www.pythian.com/blogs/1108/its-not-dead-its-just-resting-aka-mysql-ethics-and-death</link>
	<description>News and views from Pythian DBAs</description>
	<pubDate>Thu,  4 Dec 2008 23:50:37 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.5</generator>
		<item>
		<title>By: Alex Gorbachev</title>
		<link>http://www.pythian.com/blogs/1108/its-not-dead-its-just-resting-aka-mysql-ethics-and-death#comment-234991</link>
		<dc:creator>Alex Gorbachev</dc:creator>
		<pubDate>Sat, 12 Jul 2008 13:46:54 +0000</pubDate>
		<guid>http://www.pythian.com/blogs/1108/its-not-dead-its-just-resting-aka-mysql-ethics-and-death#comment-234991</guid>
		<description>&lt;i&gt;"Putting together a build or a tarball is not a trivial task for a piece of sofware as big and complex as MySQL has become."&lt;/i&gt;

One the most attractive sides of MySQL for me was always simplicity. Looks like it becomes less relevant these days which is rather unfortunate, IMHO.</description>
		<content:encoded><![CDATA[<p><i>&#8220;Putting together a build or a tarball is not a trivial task for a piece of sofware as big and complex as MySQL has become.&#8221;</i></p>
<p>One the most attractive sides of MySQL for me was always simplicity. Looks like it becomes less relevant these days which is rather unfortunate, IMHO.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve</title>
		<link>http://www.pythian.com/blogs/1108/its-not-dead-its-just-resting-aka-mysql-ethics-and-death#comment-234804</link>
		<dc:creator>Steve</dc:creator>
		<pubDate>Sat, 12 Jul 2008 03:50:06 +0000</pubDate>
		<guid>http://www.pythian.com/blogs/1108/its-not-dead-its-just-resting-aka-mysql-ethics-and-death#comment-234804</guid>
		<description>It is not "only GPL if your application is open source." That is simply not correct. Read the license, ask a lawyer. There is no such provision.</description>
		<content:encoded><![CDATA[<p>It is not &#8220;only GPL if your application is open source.&#8221; That is simply not correct. Read the license, ask a lawyer. There is no such provision.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gerry</title>
		<link>http://www.pythian.com/blogs/1108/its-not-dead-its-just-resting-aka-mysql-ethics-and-death#comment-233926</link>
		<dc:creator>Gerry</dc:creator>
		<pubDate>Fri, 11 Jul 2008 00:12:58 +0000</pubDate>
		<guid>http://www.pythian.com/blogs/1108/its-not-dead-its-just-resting-aka-mysql-ethics-and-death#comment-233926</guid>
		<description>Since I used to work for MySQL, I have my own opinion. I didn't work in the Engineering department, but the question of the frequency of Community releases was a subject of occasional conversations where I expressed my opinion.&#160;The way I see it, it is a question of resources. Putting together a build or a tarball is not a trivial task for a piece of sofware as big and complex as MySQL has become. The package of source files has to be consistent with the patches and improvements that have been made since the previous publications, a task that takes some time to do. Since the same team prepares the Enterprise and beta releases, under the pressure to release 5.1, is likely to be overwhelmed and the Community releases are not done.&#160; Where I believe Sun can help is providing the necessary resources to have at least one person dedicated to mantain and build the Community version and dedicate whatever free time this person might have, to help on the other tasks ... not the other way around (the regular build team wait for available time to prepare the Community releases). My $.02 </description>
		<content:encoded><![CDATA[<p>Since I used to work for MySQL, I have my own opinion. I didn&#8217;t work in the Engineering department, but the question of the frequency of Community releases was a subject of occasional conversations where I expressed my opinion.&nbsp;The way I see it, it is a question of resources. Putting together a build or a tarball is not a trivial task for a piece of sofware as big and complex as MySQL has become. The package of source files has to be consistent with the patches and improvements that have been made since the previous publications, a task that takes some time to do. Since the same team prepares the Enterprise and beta releases, under the pressure to release 5.1, is likely to be overwhelmed and the Community releases are not done.&nbsp; Where I believe Sun can help is providing the necessary resources to have at least one person dedicated to mantain and build the Community version and dedicate whatever free time this person might have, to help on the other tasks &#8230; not the other way around (the regular build team wait for available time to prepare the Community releases). My $.02</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sheeri Cabral</title>
		<link>http://www.pythian.com/blogs/1108/its-not-dead-its-just-resting-aka-mysql-ethics-and-death#comment-233599</link>
		<dc:creator>Sheeri Cabral</dc:creator>
		<pubDate>Thu, 10 Jul 2008 13:25:35 +0000</pubDate>
		<guid>http://www.pythian.com/blogs/1108/its-not-dead-its-just-resting-aka-mysql-ethics-and-death#comment-233599</guid>
		<description>I appreciate the clarifications; I'm interested in how folks feel about the rest of the article and the points made.</description>
		<content:encoded><![CDATA[<p>I appreciate the clarifications; I&#8217;m interested in how folks feel about the rest of the article and the points made.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ingrid Voigt</title>
		<link>http://www.pythian.com/blogs/1108/its-not-dead-its-just-resting-aka-mysql-ethics-and-death#comment-233332</link>
		<dc:creator>Ingrid Voigt</dc:creator>
		<pubDate>Thu, 10 Jul 2008 04:51:46 +0000</pubDate>
		<guid>http://www.pythian.com/blogs/1108/its-not-dead-its-just-resting-aka-mysql-ethics-and-death#comment-233332</guid>
		<description>It's only GPL if your application is open source. Otherwise, you need at least the cheapest commercial license (which, incidentally, comes with a bit of support).</description>
		<content:encoded><![CDATA[<p>It&#8217;s only GPL if your application is open source. Otherwise, you need at least the cheapest commercial license (which, incidentally, comes with a bit of support).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Arjen Lentz</title>
		<link>http://www.pythian.com/blogs/1108/its-not-dead-its-just-resting-aka-mysql-ethics-and-death#comment-233147</link>
		<dc:creator>Arjen Lentz</dc:creator>
		<pubDate>Wed, 09 Jul 2008 23:35:50 +0000</pubDate>
		<guid>http://www.pythian.com/blogs/1108/its-not-dead-its-just-resting-aka-mysql-ethics-and-death#comment-233147</guid>
		<description>License? It's all GPL.
You mean support subscription (which entitles you to the Enterprise builds directly rather than having to go via mirror.provenscaling.com)
It's definitely not about licensing!</description>
		<content:encoded><![CDATA[<p>License? It&#8217;s all GPL.<br />
You mean support subscription (which entitles you to the Enterprise builds directly rather than having to go via mirror.provenscaling.com)<br />
It&#8217;s definitely not about licensing!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
