<?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/"
	
	xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: How We Mass Upgrade Blogs</title>
	<atom:link href="http://technosailor.com/2007/01/07/how-we-mass-upgrade-blogs/feed/" rel="self" type="application/rss+xml" />
	<link>http://technosailor.com/2007/01/07/how-we-mass-upgrade-blogs/</link>
	<description>Business and Technology with Common Sense</description>
	<lastBuildDate>Fri, 10 Feb 2012 15:20:04 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4-alpha-19888</generator>
	<item>
		<title>By: b5media - Brian Layman Joins Tech Team</title>
		<link>http://technosailor.com/2007/01/07/how-we-mass-upgrade-blogs/comment-page-1/#comment-41412</link>
		<dc:creator>b5media - Brian Layman Joins Tech Team</dc:creator>
		<pubDate>Mon, 30 Apr 2007 14:04:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.technosailor.com/how-we-mass-upgrade-blogs/#comment-41412</guid>
		<description>[...] he released his own tool for upgrading WordPress blogs and I followed shortly thereafter with the script I developed for use at b5media. He has supposedly recanted his sacrilege in return for us hiring [...]</description>
		<content:encoded><![CDATA[<p>[...] he released his own tool for upgrading WordPress blogs and I followed shortly thereafter with the script I developed for use at b5media. He has supposedly recanted his sacrilege in return for us hiring [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Around the web &#124; alexking.org</title>
		<link>http://technosailor.com/2007/01/07/how-we-mass-upgrade-blogs/comment-page-1/#comment-41411</link>
		<dc:creator>Around the web &#124; alexking.org</dc:creator>
		<pubDate>Sun, 21 Jan 2007 19:09:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.technosailor.com/how-we-mass-upgrade-blogs/#comment-41411</guid>
		<description>[...] How We Mass Upgrade Blogs - Technology, Blogging and New Media [...]</description>
		<content:encoded><![CDATA[<p>[...] How We Mass Upgrade Blogs &#8211; Technology, Blogging and New Media [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: HART-Empire.com &#187; Quickies - January 15, 2007 (HART-EMPIRE NETWORK)</title>
		<link>http://technosailor.com/2007/01/07/how-we-mass-upgrade-blogs/comment-page-1/#comment-41410</link>
		<dc:creator>HART-Empire.com &#187; Quickies - January 15, 2007 (HART-EMPIRE NETWORK)</dc:creator>
		<pubDate>Mon, 15 Jan 2007 07:10:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.technosailor.com/how-we-mass-upgrade-blogs/#comment-41410</guid>
		<description>[...] to the same level .. I wish I could utililize a mass automated upgrade process &#8230; like Aaron Brazell  suggests &#8230; but I&#8217;m not quite ready (knowledgable-wise) to implement something like [...]</description>
		<content:encoded><![CDATA[<p>[...] to the same level .. I wish I could utililize a mass automated upgrade process &#8230; like Aaron Brazell  suggests &#8230; but I&#8217;m not quite ready (knowledgable-wise) to implement something like [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: HART (1-800-HART)</title>
		<link>http://technosailor.com/2007/01/07/how-we-mass-upgrade-blogs/comment-page-1/#comment-41409</link>
		<dc:creator>HART (1-800-HART)</dc:creator>
		<pubDate>Sat, 13 Jan 2007 20:04:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.technosailor.com/how-we-mass-upgrade-blogs/#comment-41409</guid>
		<description>There are also issues too, with WPMU .. I&#039;m running a version at http://PetLvr-Blogs.com however, I&#039;m just playing now :)</description>
		<content:encoded><![CDATA[<p>There are also issues too, with WPMU .. I&#8217;m running a version at <a href="http://PetLvr-Blogs.com" >http://PetLvr-Blogs.com</a> however, I&#8217;m just playing now :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aaron Brazell</title>
		<link>http://technosailor.com/2007/01/07/how-we-mass-upgrade-blogs/comment-page-1/#comment-41408</link>
		<dc:creator>Aaron Brazell</dc:creator>
		<pubDate>Sat, 13 Jan 2007 20:00:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.technosailor.com/how-we-mass-upgrade-blogs/#comment-41408</guid>
		<description>The WordPress philosophy is for the individual blogs and bloggers. Very little is done to assist in Enterprise. That&#039;s not a knock against WordPress. Just that they can&#039;t be all things to all people.

Microsoft recognized this for a long time now - which is why, among other things, they have Windows XP Home and Windows XP Pro.

The best chance there is for a WordPress that is gerared to enterprise is a fork.

We&#039;re content with what we have to do now, so we&#039;re not pushing for a fork. But a fork would be useful as more big businesses running multiple instalations of WordPress come to the forefront.

For the record, it is difficult for anyone to maintain WordPress on our scale without dealing with systems stuff - that is, getting outside of WordPress immediate.

Then there is WPMU.</description>
		<content:encoded><![CDATA[<p>The WordPress philosophy is for the individual blogs and bloggers. Very little is done to assist in Enterprise. That&#8217;s not a knock against WordPress. Just that they can&#8217;t be all things to all people.</p>
<p>Microsoft recognized this for a long time now &#8211; which is why, among other things, they have Windows XP Home and Windows XP Pro.</p>
<p>The best chance there is for a WordPress that is gerared to enterprise is a fork.</p>
<p>We&#8217;re content with what we have to do now, so we&#8217;re not pushing for a fork. But a fork would be useful as more big businesses running multiple instalations of WordPress come to the forefront.</p>
<p>For the record, it is difficult for anyone to maintain WordPress on our scale without dealing with systems stuff &#8211; that is, getting outside of WordPress immediate.</p>
<p>Then there is WPMU.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: HART (1-800-HART)</title>
		<link>http://technosailor.com/2007/01/07/how-we-mass-upgrade-blogs/comment-page-1/#comment-41407</link>
		<dc:creator>HART (1-800-HART)</dc:creator>
		<pubDate>Sat, 13 Jan 2007 19:55:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.technosailor.com/how-we-mass-upgrade-blogs/#comment-41407</guid>
		<description>Well, thanks for clearing that up (I wasn&#039;t really hounding, was I?)

I&#039;m not sure something like this would be suitable for me - at this stage. And, I have no clue what that thing about the comments and domain have to do anything about it, but that&#039;s beside the point. I have two ISPs .. one is on Windows not unix, and the other is a Reseller Account with it&#039;s own issues and individual logins, split among many individual servers.

Rather than take a crash course in Computer programming, I now see the need ever more to try and join the crowd in influencing WORDPRESS to just include an automatic upgrade!

Thanks for sharing.</description>
		<content:encoded><![CDATA[<p>Well, thanks for clearing that up (I wasn&#8217;t really hounding, was I?)</p>
<p>I&#8217;m not sure something like this would be suitable for me &#8211; at this stage. And, I have no clue what that thing about the comments and domain have to do anything about it, but that&#8217;s beside the point. I have two ISPs .. one is on Windows not unix, and the other is a Reseller Account with it&#8217;s own issues and individual logins, split among many individual servers.</p>
<p>Rather than take a crash course in Computer programming, I now see the need ever more to try and join the crowd in influencing WORDPRESS to just include an automatic upgrade!</p>
<p>Thanks for sharing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeremy Wright</title>
		<link>http://technosailor.com/2007/01/07/how-we-mass-upgrade-blogs/comment-page-1/#comment-41406</link>
		<dc:creator>Jeremy Wright</dc:creator>
		<pubDate>Mon, 08 Jan 2007 00:43:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.technosailor.com/how-we-mass-upgrade-blogs/#comment-41406</guid>
		<description>I&#039;d like to note that this is really only a part of an ever-evolving picture. Aaron&#039;s done a fantastic job at nudging us towards a more centralized and managed environment and tools like this certainly don&#039;t hurt ;-)</description>
		<content:encoded><![CDATA[<p>I&#8217;d like to note that this is really only a part of an ever-evolving picture. Aaron&#8217;s done a fantastic job at nudging us towards a more centralized and managed environment and tools like this certainly don&#8217;t hurt ;-)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aaron Brazell</title>
		<link>http://technosailor.com/2007/01/07/how-we-mass-upgrade-blogs/comment-page-1/#comment-41405</link>
		<dc:creator>Aaron Brazell</dc:creator>
		<pubDate>Sun, 07 Jan 2007 18:42:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.technosailor.com/how-we-mass-upgrade-blogs/#comment-41405</guid>
		<description>Yep. Couldn&#039;t survive without you, Sean. :)</description>
		<content:encoded><![CDATA[<p>Yep. Couldn&#8217;t survive without you, Sean. :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sean</title>
		<link>http://technosailor.com/2007/01/07/how-we-mass-upgrade-blogs/comment-page-1/#comment-41404</link>
		<dc:creator>Sean</dc:creator>
		<pubDate>Sun, 07 Jan 2007 15:43:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.technosailor.com/how-we-mass-upgrade-blogs/#comment-41404</guid>
		<description>As a guy who had a hand in other parts of the b5 setup I&#039;ll add another note about consistency:  Pretty much everything is done by scripts.  The comment field has the domain name in it because the account creation routines did it.  That way we can use scripts like the mass upgrade one.

Sean (who does paid consulting on Linux stuff too :) )</description>
		<content:encoded><![CDATA[<p>As a guy who had a hand in other parts of the b5 setup I&#8217;ll add another note about consistency:  Pretty much everything is done by scripts.  The comment field has the domain name in it because the account creation routines did it.  That way we can use scripts like the mass upgrade one.</p>
<p>Sean (who does paid consulting on Linux stuff too :) )</p>
]]></content:encoded>
	</item>
</channel>
</rss>

