<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: MySQL Binaries availability</title>
	<atom:link href="http://www.mysqlperformanceblog.com/2007/01/19/mysql-binaries-availability/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mysqlperformanceblog.com/2007/01/19/mysql-binaries-availability/</link>
	<description>Everything about MySQL Performance</description>
	<lastBuildDate>Sat, 21 Nov 2009 05:23:57 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Oleg</title>
		<link>http://www.mysqlperformanceblog.com/2007/01/19/mysql-binaries-availability/comment-page-1/#comment-222408</link>
		<dc:creator>Oleg</dc:creator>
		<pubDate>Sun, 23 Dec 2007 07:23:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2007/01/19/mysql-binaries-availability/#comment-222408</guid>
		<description>&quot;I guess having bug fixes promptly available is one of the selling points of MySQL Enterprise.&quot;
To be frank, this sucks! Since all that enterprise stuff started, binaries are published on mysql.org much-much less frequently. I&#039;ve been waiting for build containing a fix (version .48) forever... And still waiting.
I am all sad because I started with mysql for its easiness and friendliness. I do not know how to build it for Win platform, and I do not want to know, I like the comfort and convenience of getting official binaries. And now that stopped. Sad, sad...
Needless to say, if going with mysql enterprise (i.e. spend money), I would consider M$&#039;s product for more features and better query optimizer...</description>
		<content:encoded><![CDATA[<p>&#8220;I guess having bug fixes promptly available is one of the selling points of MySQL Enterprise.&#8221;<br />
To be frank, this sucks! Since all that enterprise stuff started, binaries are published on mysql.org much-much less frequently. I&#8217;ve been waiting for build containing a fix (version .48) forever&#8230; And still waiting.<br />
I am all sad because I started with mysql for its easiness and friendliness. I do not know how to build it for Win platform, and I do not want to know, I like the comfort and convenience of getting official binaries. And now that stopped. Sad, sad&#8230;<br />
Needless to say, if going with mysql enterprise (i.e. spend money), I would consider M$&#8217;s product for more features and better query optimizer&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: blog.cheyer.biz &#187; Blog Archive &#187; DorsalSource has launched!</title>
		<link>http://www.mysqlperformanceblog.com/2007/01/19/mysql-binaries-availability/comment-page-1/#comment-113657</link>
		<dc:creator>blog.cheyer.biz &#187; Blog Archive &#187; DorsalSource has launched!</dc:creator>
		<pubDate>Tue, 24 Apr 2007 20:54:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2007/01/19/mysql-binaries-availability/#comment-113657</guid>
		<description>[...] MySQL-released community binaries or else they need to build the binary themselves. Peter Zaitsev blogged at the time that he is hoping the community will establish trusted sources of MySQL builds for [...]</description>
		<content:encoded><![CDATA[<p>[...] MySQL-released community binaries or else they need to build the binary themselves. Peter Zaitsev blogged at the time that he is hoping the community will establish trusted sources of MySQL builds for [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pythian Group Blog &#187; Log Buffer #29: a Carnival of the Vanities for DBAs</title>
		<link>http://www.mysqlperformanceblog.com/2007/01/19/mysql-binaries-availability/comment-page-1/#comment-76469</link>
		<dc:creator>Pythian Group Blog &#187; Log Buffer #29: a Carnival of the Vanities for DBAs</dc:creator>
		<pubDate>Sat, 10 Mar 2007 02:50:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2007/01/19/mysql-binaries-availability/#comment-76469</guid>
		<description>[...] Zaitsev likewise weighs in on the MySQL Performance Blog: &#8220;For many users running old MySQL binary is not the problem, [...]</description>
		<content:encoded><![CDATA[<p>[...] Zaitsev likewise weighs in on the MySQL Performance Blog: &#8220;For many users running old MySQL binary is not the problem, [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard Fearn &#187; Building MySQL from source</title>
		<link>http://www.mysqlperformanceblog.com/2007/01/19/mysql-binaries-availability/comment-page-1/#comment-60211</link>
		<dc:creator>Richard Fearn &#187; Building MySQL from source</dc:creator>
		<pubDate>Sun, 25 Feb 2007 14:44:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2007/01/19/mysql-binaries-availability/#comment-60211</guid>
		<description>[...] the meantime, you can either find an unofficial build, or build MySQL yourself. I decided to try and build it myself using the free edition of Visual [...]</description>
		<content:encoded><![CDATA[<p>[...] the meantime, you can either find an unofficial build, or build MySQL yourself. I decided to try and build it myself using the free edition of Visual [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Day</title>
		<link>http://www.mysqlperformanceblog.com/2007/01/19/mysql-binaries-availability/comment-page-1/#comment-35379</link>
		<dc:creator>James Day</dc:creator>
		<pubDate>Tue, 23 Jan 2007 17:55:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2007/01/19/mysql-binaries-availability/#comment-35379</guid>
		<description>&quot;We use the following policy when updating MySQL: 

Enterprise Server releases are meant to appear every 18 months, supplemented by quarterly service packs and monthly rapid updates. Community Server releases are meant to appear 2–3 times per year.&quot;

http://dev.mysql.com/doc/refman/5.0/en/many-versions.html</description>
		<content:encoded><![CDATA[<p>&#8220;We use the following policy when updating MySQL: </p>
<p>Enterprise Server releases are meant to appear every 18 months, supplemented by quarterly service packs and monthly rapid updates. Community Server releases are meant to appear 2–3 times per year.&#8221;</p>
<p><a href="http://dev.mysql.com/doc/refman/5.0/en/many-versions.html" rel="nofollow">http://dev.mysql.com/doc/refman/5.0/en/many-versions.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Day</title>
		<link>http://www.mysqlperformanceblog.com/2007/01/19/mysql-binaries-availability/comment-page-1/#comment-34556</link>
		<dc:creator>James Day</dc:creator>
		<pubDate>Mon, 22 Jan 2007 07:16:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2007/01/19/mysql-binaries-availability/#comment-34556</guid>
		<description>Peter Laursen, if you have not changed the name, please add &quot;built by &quot; to the version so that it is possible to identify who is affected by compiler, build or library bugs that may be in a particular build. I don&#039;t suggest that your build is bad, just that these things happen and we need a way to identify the build if there is a problem discovered later. It also helps to know what version is needed to match core dumps if there is a crash problem.

This request is just to make support easier. It&#039;s not an official statement by MySQL about how the trademark for MySQL&#039;s Community or Enterprise servers should be used in builds. I don&#039;t know if MySQL will have an official view on that or what it will be. Please don&#039;t stop building because of this possibility - I trust that MySQL will be nice about it if it wants a change. About the worst you&#039;re likely to get is a polite letter from someone in MySQL&#039;s Community team asking you to make a change and saying sorry for the inconvenience.</description>
		<content:encoded><![CDATA[<p>Peter Laursen, if you have not changed the name, please add &#8220;built by &#8221; to the version so that it is possible to identify who is affected by compiler, build or library bugs that may be in a particular build. I don&#8217;t suggest that your build is bad, just that these things happen and we need a way to identify the build if there is a problem discovered later. It also helps to know what version is needed to match core dumps if there is a crash problem.</p>
<p>This request is just to make support easier. It&#8217;s not an official statement by MySQL about how the trademark for MySQL&#8217;s Community or Enterprise servers should be used in builds. I don&#8217;t know if MySQL will have an official view on that or what it will be. Please don&#8217;t stop building because of this possibility &#8211; I trust that MySQL will be nice about it if it wants a change. About the worst you&#8217;re likely to get is a polite letter from someone in MySQL&#8217;s Community team asking you to make a change and saying sorry for the inconvenience.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Planeta Fedora &#187; Getting emo over binaries?</title>
		<link>http://www.mysqlperformanceblog.com/2007/01/19/mysql-binaries-availability/comment-page-1/#comment-33224</link>
		<dc:creator>Planeta Fedora &#187; Getting emo over binaries?</dc:creator>
		<pubDate>Sat, 20 Jan 2007 05:45:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2007/01/19/mysql-binaries-availability/#comment-33224</guid>
		<description>[...] So, if you see a binary once every six months, how is that rarely released? We’re not expecting Windows users to compile away. [...]</description>
		<content:encoded><![CDATA[<p>[...] So, if you see a binary once every six months, how is that rarely released? We’re not expecting Windows users to compile away. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter Laursen</title>
		<link>http://www.mysqlperformanceblog.com/2007/01/19/mysql-binaries-availability/comment-page-1/#comment-33193</link>
		<dc:creator>Peter Laursen</dc:creator>
		<pubDate>Sat, 20 Jan 2007 05:02:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2007/01/19/mysql-binaries-availability/#comment-33193</guid>
		<description>Webyog provides 5.0.33 for download.
(installer version for Windows only).

http://www.webyog.com/forums//index.php?showtopic=2988</description>
		<content:encoded><![CDATA[<p>Webyog provides 5.0.33 for download.<br />
(installer version for Windows only).</p>
<p><a href="http://www.webyog.com/forums//index.php?showtopic=2988" rel="nofollow">http://www.webyog.com/forums//index.php?showtopic=2988</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Damien Seguy</title>
		<link>http://www.mysqlperformanceblog.com/2007/01/19/mysql-binaries-availability/comment-page-1/#comment-32728</link>
		<dc:creator>Damien Seguy</dc:creator>
		<pubDate>Fri, 19 Jan 2007 12:50:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2007/01/19/mysql-binaries-availability/#comment-32728</guid>
		<description>dotdeb.org is providing MySQL 5.0.x unofficial packages, including enterprise versions.

http://www.dotdeb.org/news

5.0.33 is not there yet, but 5.0.32 is available with apt-get install.

unofficial debian PHP packages are alsol available there, both for i386 and amd64.

May be those comments will collet quite a number of unofficial MySQL built, just like Kaj hopes about.</description>
		<content:encoded><![CDATA[<p>dotdeb.org is providing MySQL 5.0.x unofficial packages, including enterprise versions.</p>
<p><a href="http://www.dotdeb.org/news" rel="nofollow">http://www.dotdeb.org/news</a></p>
<p>5.0.33 is not there yet, but 5.0.32 is available with apt-get install.</p>
<p>unofficial debian PHP packages are alsol available there, both for i386 and amd64.</p>
<p>May be those comments will collet quite a number of unofficial MySQL built, just like Kaj hopes about.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
