<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.2" -->
<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: Upgrade Patches Now Available!</title>
	<link>http://www.activecampaign.com/blog/2008/03/18/upgrade-patches-now-available/</link>
	<description>ActiveCampaign Development Blog - PHP, MySQL, AJAX, Linux, Programming &#038; More...</description>
	<pubDate>Tue, 06 Jan 2009 00:34:13 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.2</generator>
		<item>
		<title>By: Jason</title>
		<link>http://www.activecampaign.com/blog/2008/03/18/upgrade-patches-now-available/#comment-58153</link>
		<dc:creator>Jason</dc:creator>
		<pubDate>Wed, 19 Mar 2008 18:33:51 +0000</pubDate>
		<guid>http://www.activecampaign.com/blog/2008/03/18/upgrade-patches-now-available/#comment-58153</guid>
		<description>Thanks for the feedback!  We have added the idea of having a file that lists all the files that are included for a future release of our patch system.  If you have any other suggestions just let us know!</description>
		<content:encoded><![CDATA[<p>Thanks for the feedback!  We have added the idea of having a file that lists all the files that are included for a future release of our patch system.  If you have any other suggestions just let us know!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rowan</title>
		<link>http://www.activecampaign.com/blog/2008/03/18/upgrade-patches-now-available/#comment-58143</link>
		<dc:creator>Rowan</dc:creator>
		<pubDate>Wed, 19 Mar 2008 15:01:02 +0000</pubDate>
		<guid>http://www.activecampaign.com/blog/2008/03/18/upgrade-patches-now-available/#comment-58143</guid>
		<description>Just tried this out for Triolive and (touch wood) it appears to work well. Any chance of including a text file in the provided archive with a list of the included files? (and possibly the obsoleted ones) This would make manual checking against customisations easier and especially when upgrading through multiple versions.</description>
		<content:encoded><![CDATA[<p>Just tried this out for Triolive and (touch wood) it appears to work well. Any chance of including a text file in the provided archive with a list of the included files? (and possibly the obsoleted ones) This would make manual checking against customisations easier and especially when upgrading through multiple versions.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
