<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.1.3" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: How to Notify Your Customers About Software Update Safely</title>
	<link>http://www.drexplain.com/isv-kaizen-blog/distribution/how-to-notify-your-customers-about-software-update-safely/</link>
	<description>Strategy of continuous improvement for ISV business</description>
	<pubDate>Thu, 29 Jul 2010 14:24:26 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.1.3</generator>

	<item>
		<title>By: Tim Haughton</title>
		<link>http://www.drexplain.com/isv-kaizen-blog/distribution/how-to-notify-your-customers-about-software-update-safely/#comment-790</link>
		<author>Tim Haughton</author>
		<pubDate>Sat, 14 Mar 2009 07:48:05 +0000</pubDate>
		<guid>http://www.drexplain.com/isv-kaizen-blog/distribution/how-to-notify-your-customers-about-software-update-safely/#comment-790</guid>
					<description>For my document management software, I use a combination of weekly updates and ClickOnce to achieve update nirvana. The weekly updates mean that there is seldom an epic change coming into any 1 release, and the changes happen progressively over time.

ClickOnce has the benefit that I publish the change to my server, and the application is updated automagically on customers' machines.</description>
		<content:encoded><![CDATA[<p>For my document management software, I use a combination of weekly updates and ClickOnce to achieve update nirvana. The weekly updates mean that there is seldom an epic change coming into any 1 release, and the changes happen progressively over time.</p>
<p>ClickOnce has the benefit that I publish the change to my server, and the application is updated automagically on customers&#8217; machines.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Dennis Crane</title>
		<link>http://www.drexplain.com/isv-kaizen-blog/distribution/how-to-notify-your-customers-about-software-update-safely/#comment-791</link>
		<author>Dennis Crane</author>
		<pubDate>Sat, 14 Mar 2009 16:01:24 +0000</pubDate>
		<guid>http://www.drexplain.com/isv-kaizen-blog/distribution/how-to-notify-your-customers-about-software-update-safely/#comment-791</guid>
					<description>Excellent hint, Tim. I agree that 'Check for update' feature will simplify the task. 
In the same time my tip may be useful also for cases when you need to tell the users something more than just 'We have an update', e.g. announcing a special offer or other news . Sometimes we have to send e-mails.</description>
		<content:encoded><![CDATA[<p>Excellent hint, Tim. I agree that &#8216;Check for update&#8217; feature will simplify the task.<br />
In the same time my tip may be useful also for cases when you need to tell the users something more than just &#8216;We have an update&#8217;, e.g. announcing a special offer or other news . Sometimes we have to send e-mails.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Dennis Crane</title>
		<link>http://www.drexplain.com/isv-kaizen-blog/distribution/how-to-notify-your-customers-about-software-update-safely/#comment-792</link>
		<author>Dennis Crane</author>
		<pubDate>Tue, 17 Mar 2009 19:50:27 +0000</pubDate>
		<guid>http://www.drexplain.com/isv-kaizen-blog/distribution/how-to-notify-your-customers-about-software-update-safely/#comment-792</guid>
					<description>BTW, Tim, the ‘Check for update’ feature doesn't help or will even harm if you have an issue in your release. 
As the release gets visible to all users in a moment, they all will download the file with issue. You won't have a chance to fix it quickly.</description>
		<content:encoded><![CDATA[<p>BTW, Tim, the ‘Check for update’ feature doesn&#8217;t help or will even harm if you have an issue in your release.<br />
As the release gets visible to all users in a moment, they all will download the file with issue. You won&#8217;t have a chance to fix it quickly.</p>
]]></content:encoded>
				</item>
</channel>
</rss>
