<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Digital Signage Blog &#187; Bugs</title>
	<atom:link href="http://www.digitalsignageblog.com/tag/bugs/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.digitalsignageblog.com</link>
	<description>Digital signage blog - the blog of digital signage</description>
	<lastBuildDate>Tue, 31 Jan 2012 01:54:10 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>To upgrade or not to upgrade&#8230; that is the question!</title>
		<link>http://www.digitalsignageblog.com/2009/09/18/to-upgrade-or-not-to-upgrade-that-is-the-question/</link>
		<comments>http://www.digitalsignageblog.com/2009/09/18/to-upgrade-or-not-to-upgrade-that-is-the-question/#comments</comments>
		<pubDate>Fri, 18 Sep 2009 04:45:24 +0000</pubDate>
		<dc:creator>DigitalSignageBlog</dc:creator>
				<category><![CDATA[Digital Signage Blog News]]></category>
		<category><![CDATA[Amount Of Time]]></category>
		<category><![CDATA[Best Interest]]></category>
		<category><![CDATA[Bugs]]></category>
		<category><![CDATA[Client Request]]></category>
		<category><![CDATA[Developers]]></category>
		<category><![CDATA[digital signage]]></category>
		<category><![CDATA[Digital Signage Software]]></category>
		<category><![CDATA[Dilemma]]></category>
		<category><![CDATA[Doings]]></category>
		<category><![CDATA[environment]]></category>
		<category><![CDATA[Faith]]></category>
		<category><![CDATA[Job]]></category>
		<category><![CDATA[Latest Software]]></category>
		<category><![CDATA[Patches]]></category>
		<category><![CDATA[Rollback]]></category>
		<category><![CDATA[Scenarios]]></category>
		<category><![CDATA[Signage Company]]></category>
		<category><![CDATA[Signage Solution]]></category>
		<category><![CDATA[Software Company]]></category>
		<category><![CDATA[Software Component]]></category>
		<category><![CDATA[Software Patch]]></category>
		<category><![CDATA[Solution Provider]]></category>
		<category><![CDATA[System Software]]></category>
		<category><![CDATA[Test Environment]]></category>
		<category><![CDATA[Test Software]]></category>
		<category><![CDATA[Test Unit]]></category>
		<category><![CDATA[Uni]]></category>
		<category><![CDATA[Working Solution]]></category>

		<guid isPermaLink="false">http://www.digitalsignageblog.com/?p=1611</guid>
		<description><![CDATA[Sometimes being a digital signage solution provider can be a tough and challenging job. Not only do you have to represent the company you&#8217;re selling the product for but you&#8217;re also consciously looking after the best interest for the client and here&#8217;s a typical dilemma: One of our clients requested a feature to a digital [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.digitalsignageblog.com/wp-content/uploads/2009/09/version.jpg" rel="thumbnail"><img class="alignleft size-medium wp-image-1628" title="Digital Signage Version - to upgrade or not to upgrade" src="wp-content/uploads/cache/7017cfa2cb707d60e8ca56ec75e06945.jpg" alt="Digital Signage Version - to upgrade or not to upgrade" width="162" height="132" /></a>Sometimes being a <span class='bm_keywordlink'><a href="http://www.advertiseme.com.au" target="_blank">digital signage</a></span> solution provider can be a tough and challenging job. Not only do you have to represent the company you&#8217;re selling the product for but you&#8217;re also consciously looking after the best interest for the client and here&#8217;s a typical dilemma:</p>
<p>One of our clients requested a feature to a digital signage software component which wasn&#8217;t that much of an issue except we required the services of the digital signage software company and  there was a cost associated with this feature (the client was happy to pay for this). But all this came with  a little  unanticipated catch &#8211; the client was required to upgrade to the  latest version of the software before the modification patch would work. Many of us might be thinking,  &#8220;That&#8217;s easy, there&#8217;s no harm in doings so as the latest patch will resolve and fix previous bugs&#8221;&#8230;. Ummmmmm&#8230;. WRONG!!!</p>
<p>By upgrading the software we found quite a number of bugs and spend quite a number of hours investigating and then reporting the issue to the manufacturer whilst the client had to workaround the problem. Fortunately, we provided the client with a test environment and didn&#8217;t upgrade the development system with the latest software.</p>
<p>I&#8217;m not sure whether many of you have experienced this but upgrading to the latest version can actually introduce new bugs. What&#8217;s worse is that a considerable amount of time can be  spent investigating the issue and the  time for this may not be chargeable &#8211; who do you charge for this type of work&#8230;. the client who has already paid for a working solution ? or the digital signage company who supplied the dodgy software?</p>
<p>This is a tough one and I&#8217;ll like to hear from anyone who has been through this experience.</p>
<p>So there are a few lessons that I have learnt from this:</p>
<p><strong>1. ALWAYS</strong> make sure you test the upgrade or software patch on a test unit or environment</p>
<p><strong>2. ALWAYS</strong> back up your content or system before applying any patches as you&#8217;ll  never know the state of the unit after the reboot</p>
<p><strong>3. PLAN</strong> for any changes you make to the system and carefully provide detailed rollback plans in the event the change failed</p>
<p><strong>4. TRUST</strong> and have some faith that the developers have done their testing but acknowledge that they cannot test all the different scenarios</p>
<p><strong>5.</strong> Make sure you charge someone for your work or include this as part of your Maintenance and Support costs&#8230; or even better get the manufacturer to conduct intensive testing with your configuration before applying any patches or upgrades</p>
<p><strong>6. IF IT&#8217;S NOT BROKEN LEAVE IT AS IT IS</strong>&#8230; sometimes making a simple change can break the entire system&#8230; but if you&#8217;ve done the above point 2 &amp; 3 correctly then this shouldn&#8217;t be an issue.</p>
<p><br class="spacer_" /></p>
<blockquote><p>Have you been in this situation? Tell us what you think.</p>
</blockquote>
<p><br class="spacer_" /></p>
<p><em>Feel free to submit your answer as a comment.</em></p>
<p><br class="spacer_" /></p>
<p><br class="spacer_" /></p>
<p><br class="spacer_" /></p>
<p><br class="spacer_" /></p>
<p><br class="spacer_" /></p>
<hr />
<p><small>© <a href="http://www.advertiseme.com.au">AdvertiseMe.com.au</a> for <a href="http://www.digitalsignageblog.com">Digital Signage Blog</a>, 2009. |
<a href="http://www.digitalsignageblog.com/2009/09/18/to-upgrade-or-not-to-upgrade-that-is-the-question/">Permalink</a> |
<a href="http://www.digitalsignageblog.com/2009/09/18/to-upgrade-or-not-to-upgrade-that-is-the-question/#comments">No comment</a> |
<br/>
Post tags: <a href="http://www.digitalsignageblog.com/tag/amount-of-time/" rel="tag">Amount Of Time</a>, <a href="http://www.digitalsignageblog.com/tag/best-interest/" rel="tag">Best Interest</a>, <a href="http://www.digitalsignageblog.com/tag/bugs/" rel="tag">Bugs</a>, <a href="http://www.digitalsignageblog.com/tag/client-request/" rel="tag">Client Request</a>, <a href="http://www.digitalsignageblog.com/tag/developers/" rel="tag">Developers</a>, <a href="http://www.digitalsignageblog.com/tag/digital-signage/" rel="tag">digital signage</a>, <a href="http://www.digitalsignageblog.com/tag/digital-signage-software/" rel="tag">Digital Signage Software</a>, <a href="http://www.digitalsignageblog.com/tag/dilemma/" rel="tag">Dilemma</a>, <a href="http://www.digitalsignageblog.com/tag/doings/" rel="tag">Doings</a>, <a href="http://www.digitalsignageblog.com/tag/environment/" rel="tag">environment</a>, <a href="http://www.digitalsignageblog.com/tag/faith/" rel="tag">Faith</a>, <a href="http://www.digitalsignageblog.com/tag/job/" rel="tag">Job</a>, <a href="http://www.digitalsignageblog.com/tag/latest-software/" rel="tag">Latest Software</a>, <a href="http://www.digitalsignageblog.com/tag/patches/" rel="tag">Patches</a>, <a href="http://www.digitalsignageblog.com/tag/rollback/" rel="tag">Rollback</a>, <a href="http://www.digitalsignageblog.com/tag/scenarios/" rel="tag">Scenarios</a>, <a href="http://www.digitalsignageblog.com/tag/signage-company/" rel="tag">Signage Company</a>, <a href="http://www.digitalsignageblog.com/tag/signage-solution/" rel="tag">Signage Solution</a>, <a href="http://www.digitalsignageblog.com/tag/software-company/" rel="tag">Software Company</a>, <a href="http://www.digitalsignageblog.com/tag/software-component/" rel="tag">Software Component</a>, <a href="http://www.digitalsignageblog.com/tag/software-patch/" rel="tag">Software Patch</a>, <a href="http://www.digitalsignageblog.com/tag/solution-provider/" rel="tag">Solution Provider</a>, <a href="http://www.digitalsignageblog.com/tag/system-software/" rel="tag">System Software</a>, <a href="http://www.digitalsignageblog.com/tag/test-environment/" rel="tag">Test Environment</a>, <a href="http://www.digitalsignageblog.com/tag/test-software/" rel="tag">Test Software</a>, <a href="http://www.digitalsignageblog.com/tag/test-unit/" rel="tag">Test Unit</a>, <a href="http://www.digitalsignageblog.com/tag/uni/" rel="tag">Uni</a>, <a href="http://www.digitalsignageblog.com/tag/working-solution/" rel="tag">Working Solution</a><br/>
</small></p>]]></content:encoded>
			<wfw:commentRss>http://www.digitalsignageblog.com/2009/09/18/to-upgrade-or-not-to-upgrade-that-is-the-question/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

