<?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: A note about Nightly Tester Tools</title>
	<atom:link href="http://ilias.ca/blog/2006/10/a-note-about-nightly-tester-tools/feed/" rel="self" type="application/rss+xml" />
	<link>http://ilias.ca/blog/2006/10/a-note-about-nightly-tester-tools/</link>
	<description>I still dream of Organon</description>
	<lastBuildDate>Mon, 14 May 2012 23:08:45 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Matt</title>
		<link>http://ilias.ca/blog/2006/10/a-note-about-nightly-tester-tools/comment-page-1/#comment-156795</link>
		<dc:creator>Matt</dc:creator>
		<pubDate>Tue, 06 Nov 2007 10:09:31 +0000</pubDate>
		<guid isPermaLink="false">http://ilias.ca/blog/2006/10/a-note-about-nightly-tester-tools/#comment-156795</guid>
		<description>Of course, the answer to that has always been the same - with or without NTT, as people were bumping extension versions a long while before - is that a user who takes the advice given frequently in the forums, and thinks a little first, has a separate &#039;Test&#039; profile into which they install every extension (bumped or not) and check to see if a problem occurs.
As we know it is the Profile that gets corrupted in the event of incompatibility.
That&#039;s why I think users should be advised to test any and every extension first, since a combination of certain (on their own, perfectly compatible with the program version) extensions in the same profile will cause a problem that didn&#039;t arise before they ended up co-existing. And no extension developer can possibly test that.</description>
		<content:encoded><![CDATA[<p>Of course, the answer to that has always been the same &#8211; with or without NTT, as people were bumping extension versions a long while before &#8211; is that a user who takes the advice given frequently in the forums, and thinks a little first, has a separate &#8216;Test&#8217; profile into which they install every extension (bumped or not) and check to see if a problem occurs.<br />
As we know it is the Profile that gets corrupted in the event of incompatibility.<br />
That&#8217;s why I think users should be advised to test any and every extension first, since a combination of certain (on their own, perfectly compatible with the program version) extensions in the same profile will cause a problem that didn&#8217;t arise before they ended up co-existing. And no extension developer can possibly test that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Greg K Nicholson</title>
		<link>http://ilias.ca/blog/2006/10/a-note-about-nightly-tester-tools/comment-page-1/#comment-2073</link>
		<dc:creator>Greg K Nicholson</dc:creator>
		<pubDate>Sat, 28 Oct 2006 03:25:56 +0000</pubDate>
		<guid isPermaLink="false">http://ilias.ca/blog/2006/10/a-note-about-nightly-tester-tools/#comment-2073</guid>
		<description>The same applies when setting extensions.checkCompatibility to false in about:config.</description>
		<content:encoded><![CDATA[<p>The same applies when setting extensions.checkCompatibility to false in about:config.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

