<?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: Major update to Firefox 3.6 (the day after)</title>
	<atom:link href="http://oduinn.com/blog/2010/01/22/major-update-to-firefox-36-the-day-after/feed/" rel="self" type="application/rss+xml" />
	<link>http://oduinn.com/blog/2010/01/22/major-update-to-firefox-36-the-day-after/</link>
	<description></description>
	<lastBuildDate>Fri, 27 Jan 2012 15:12:34 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: sr pt</title>
		<link>http://oduinn.com/blog/2010/01/22/major-update-to-firefox-36-the-day-after/#comment-44188</link>
		<dc:creator>sr pt</dc:creator>
		<pubDate>Mon, 22 Feb 2010 22:41:11 +0000</pubDate>
		<guid isPermaLink="false">http://oduinn.com/2010/01/22/major-update-to-firefox-36-the-day-after/#comment-44188</guid>
		<description>I did not know of the Help&gt;Check for Updates.</description>
		<content:encoded><![CDATA[<p>I did not know of the Help&gt;Check for Updates.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: takeshi</title>
		<link>http://oduinn.com/blog/2010/01/22/major-update-to-firefox-36-the-day-after/#comment-43887</link>
		<dc:creator>takeshi</dc:creator>
		<pubDate>Fri, 12 Feb 2010 03:33:00 +0000</pubDate>
		<guid isPermaLink="false">http://oduinn.com/2010/01/22/major-update-to-firefox-36-the-day-after/#comment-43887</guid>
		<description>If you prefer in-place upgrade than downloading installer, why not remove &quot;Get the World&#039;s Best Browser&quot; in Software Update dialog appearing after you click CheckForUpdates?
At least this should be &quot;For more information...&quot; in the last of this frame.</description>
		<content:encoded><![CDATA[<p>If you prefer in-place upgrade than downloading installer, why not remove &#8220;Get the World&#8217;s Best Browser&#8221; in Software Update dialog appearing after you click CheckForUpdates?<br />
At least this should be &#8220;For more information&#8230;&#8221; in the last of this frame.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John</title>
		<link>http://oduinn.com/blog/2010/01/22/major-update-to-firefox-36-the-day-after/#comment-43388</link>
		<dc:creator>John</dc:creator>
		<pubDate>Sat, 30 Jan 2010 05:20:17 +0000</pubDate>
		<guid isPermaLink="false">http://oduinn.com/2010/01/22/major-update-to-firefox-36-the-day-after/#comment-43388</guid>
		<description>hi;

Wow; thanks for the *tons* of replies on that post.


Trevian,Martin: possible you were just a little too quick? We only enabled the updates around 9am PST / 10am MST / 5pm GMT. If you still have a computer on FF3.5.7, can you try again?

AUser,Joris,smaug: We make major update available at the same time as the downloadable installers. We&#039;ve started doing this with the FF3.5.0 release, and with every release since then.

Gaurav,Tulapi,JimB,Matt,Peter Gasston,alanjstr: If you have more details on when you hit that &quot;No updates available&quot;, we&#039;d love to hear. I&#039;ve filed &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=543157&quot; rel=&quot;nofollow&quot;&gt;https://bugzilla.mozilla.org/show_bug.cgi?id=543157&lt;/a&gt; to track this. Any information you have would be great. Like when did you try? What city you were in at the time? What OS you were on? What version of Firefox you were running, trying to upgrade *from*?</description>
		<content:encoded><![CDATA[<p>hi;</p>
<p>Wow; thanks for the *tons* of replies on that post.</p>
<p>Trevian,Martin: possible you were just a little too quick? We only enabled the updates around 9am PST / 10am MST / 5pm GMT. If you still have a computer on FF3.5.7, can you try again?</p>
<p>AUser,Joris,smaug: We make major update available at the same time as the downloadable installers. We&#8217;ve started doing this with the FF3.5.0 release, and with every release since then.</p>
<p>Gaurav,Tulapi,JimB,Matt,Peter Gasston,alanjstr: If you have more details on when you hit that &#8220;No updates available&#8221;, we&#8217;d love to hear. I&#8217;ve filed <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=543157" rel="nofollow">https://bugzilla.mozilla.org/show_bug.cgi?id=543157</a> to track this. Any information you have would be great. Like when did you try? What city you were in at the time? What OS you were on? What version of Firefox you were running, trying to upgrade *from*?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MT</title>
		<link>http://oduinn.com/blog/2010/01/22/major-update-to-firefox-36-the-day-after/#comment-43194</link>
		<dc:creator>MT</dc:creator>
		<pubDate>Sun, 24 Jan 2010 22:04:34 +0000</pubDate>
		<guid isPermaLink="false">http://oduinn.com/2010/01/22/major-update-to-firefox-36-the-day-after/#comment-43194</guid>
		<description>It make sense to add an option to backup existing profile before installing update (and, in fact, whenever user wants to make backup). Moreover, it make sense to provide a way to create/select profiles with normal GUI rather than using sort of &quot;secret&quot; command line option -p to call the profile manager. Not all users know about profiles at all, and installing Fx from full installer may be just some desirable (but elusory) way to isolate (just in case) existing data and settings from new version.</description>
		<content:encoded><![CDATA[<p>It make sense to add an option to backup existing profile before installing update (and, in fact, whenever user wants to make backup). Moreover, it make sense to provide a way to create/select profiles with normal GUI rather than using sort of &#8220;secret&#8221; command line option -p to call the profile manager. Not all users know about profiles at all, and installing Fx from full installer may be just some desirable (but elusory) way to isolate (just in case) existing data and settings from new version.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rasmussen</title>
		<link>http://oduinn.com/blog/2010/01/22/major-update-to-firefox-36-the-day-after/#comment-43189</link>
		<dc:creator>Rasmussen</dc:creator>
		<pubDate>Sun, 24 Jan 2010 15:05:19 +0000</pubDate>
		<guid isPermaLink="false">http://oduinn.com/2010/01/22/major-update-to-firefox-36-the-day-after/#comment-43189</guid>
		<description>Updating is slow. I prefer to Dowloadthemall the binary file. And while there is a way to pause updating, there is no way to cancel it. Been doing it from 3.5. Always like to have a bacup of an old version.</description>
		<content:encoded><![CDATA[<p>Updating is slow. I prefer to Dowloadthemall the binary file. And while there is a way to pause updating, there is no way to cancel it. Been doing it from 3.5. Always like to have a bacup of an old version.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mithgol the Webmaster</title>
		<link>http://oduinn.com/blog/2010/01/22/major-update-to-firefox-36-the-day-after/#comment-43186</link>
		<dc:creator>Mithgol the Webmaster</dc:creator>
		<pubDate>Sun, 24 Jan 2010 12:36:22 +0000</pubDate>
		<guid isPermaLink="false">http://oduinn.com/2010/01/22/major-update-to-firefox-36-the-day-after/#comment-43186</guid>
		<description>First of all, complete update means you won&#039;t meet with bug 489522.

The update executable also can then be manually brought to environments with limited Internet access (intranets, expensive GPRS, etc.), where direct update is not desireable.</description>
		<content:encoded><![CDATA[<p>First of all, complete update means you won&#8217;t meet with bug 489522.</p>
<p>The update executable also can then be manually brought to environments with limited Internet access (intranets, expensive GPRS, etc.), where direct update is not desireable.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ron</title>
		<link>http://oduinn.com/blog/2010/01/22/major-update-to-firefox-36-the-day-after/#comment-43179</link>
		<dc:creator>Ron</dc:creator>
		<pubDate>Sat, 23 Jan 2010 20:16:40 +0000</pubDate>
		<guid isPermaLink="false">http://oduinn.com/2010/01/22/major-update-to-firefox-36-the-day-after/#comment-43179</guid>
		<description>I think most people have no idea Help &gt; Check for Updates exists, and assume the way to get the new version is to download it from the website.

If you want more people to use the built-in updater, then I think you&#039;re going to have to do one (or both) of the following things:

1) Educate them.  The Firefox download page needs to detect that they&#039;re using the previous version of Firefox and suggest that they use Help &gt; Check for Updates instead of downloading the entire thing.  It should also tell them why (easier, faster, smaller download, etc.).

2) Push the update notification sooner, so fewer have a chance to download it manually.  This may or may not be feasible or practical.  Either way, I doubt it would have the same success rate as #1.</description>
		<content:encoded><![CDATA[<p>I think most people have no idea Help &gt; Check for Updates exists, and assume the way to get the new version is to download it from the website.</p>
<p>If you want more people to use the built-in updater, then I think you&#8217;re going to have to do one (or both) of the following things:</p>
<p>1) Educate them.  The Firefox download page needs to detect that they&#8217;re using the previous version of Firefox and suggest that they use Help &gt; Check for Updates instead of downloading the entire thing.  It should also tell them why (easier, faster, smaller download, etc.).</p>
<p>2) Push the update notification sooner, so fewer have a chance to download it manually.  This may or may not be feasible or practical.  Either way, I doubt it would have the same success rate as #1.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kyle</title>
		<link>http://oduinn.com/blog/2010/01/22/major-update-to-firefox-36-the-day-after/#comment-43176</link>
		<dc:creator>Kyle</dc:creator>
		<pubDate>Sat, 23 Jan 2010 18:39:18 +0000</pubDate>
		<guid isPermaLink="false">http://oduinn.com/2010/01/22/major-update-to-firefox-36-the-day-after/#comment-43176</guid>
		<description>Not that it gets to the central thrust of your post, but another disadvantage of not doing CheckForUpdates is that users don&#039;t get notified if their extensions are incompatible beforehand.</description>
		<content:encoded><![CDATA[<p>Not that it gets to the central thrust of your post, but another disadvantage of not doing CheckForUpdates is that users don&#8217;t get notified if their extensions are incompatible beforehand.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jigar shah</title>
		<link>http://oduinn.com/blog/2010/01/22/major-update-to-firefox-36-the-day-after/#comment-43170</link>
		<dc:creator>Jigar shah</dc:creator>
		<pubDate>Sat, 23 Jan 2010 11:42:16 +0000</pubDate>
		<guid isPermaLink="false">http://oduinn.com/2010/01/22/major-update-to-firefox-36-the-day-after/#comment-43170</guid>
		<description>Yes you can:) less crashes on FF :) I have also experienced similar issue with update. On linux distribution like fedora, new FF comes only when maintainer gets time. So i prefer o have custom version always. But it seems thats not the right way. bcos I see lots of crashes after update on Fedora12, almost everytime i close FF. Not sure why. But will try installing fresh. (and loosing lots of configurations and preferences for addons)</description>
		<content:encoded><![CDATA[<p>Yes you can:) less crashes on FF <img src='http://oduinn.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />  I have also experienced similar issue with update. On linux distribution like fedora, new FF comes only when maintainer gets time. So i prefer o have custom version always. But it seems thats not the right way. bcos I see lots of crashes after update on Fedora12, almost everytime i close FF. Not sure why. But will try installing fresh. (and loosing lots of configurations and preferences for addons)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jabba</title>
		<link>http://oduinn.com/blog/2010/01/22/major-update-to-firefox-36-the-day-after/#comment-43165</link>
		<dc:creator>Jabba</dc:creator>
		<pubDate>Sat, 23 Jan 2010 06:38:25 +0000</pubDate>
		<guid isPermaLink="false">http://oduinn.com/2010/01/22/major-update-to-firefox-36-the-day-after/#comment-43165</guid>
		<description>I think for me, there were three reasons why I manually downloaded instead of checking for updates:

1. Being in Germany and being subscribed to Planet Mozilla, I had about 30 blogs and Tweets that told me that Firefox would be released on the 21st, but nobody told me what time. So all day I would check the website until it was finally there in the evening.

2. I don&#039;t think the average user knows that the supported upgrade path is. In the past, this has always been a little confusing. If I am using 2.0.xx and I check for updates, I&#039;d get updated to 3.0.xx. If I&#039;m using 3.0.xx and check for updates, I don&#039;t get updated. When the new release came out, I wasn&#039;t sure if that meant that 3.0.xx users would get updated to 3.5.xx and 3.6.xx would need to be a manual update, or what? So the easy thing is just to go download it manually, since I was checking the website all day for the new version anyway.

3. About half of the boxes I use run Linux, where the Check for Updates thing is grayed out and if you want to run the current version of anything, it needs to be a manual install. So I manually download it from the website and put it in /opt/, since the repositories have an older version.</description>
		<content:encoded><![CDATA[<p>I think for me, there were three reasons why I manually downloaded instead of checking for updates:</p>
<p>1. Being in Germany and being subscribed to Planet Mozilla, I had about 30 blogs and Tweets that told me that Firefox would be released on the 21st, but nobody told me what time. So all day I would check the website until it was finally there in the evening.</p>
<p>2. I don&#8217;t think the average user knows that the supported upgrade path is. In the past, this has always been a little confusing. If I am using 2.0.xx and I check for updates, I&#8217;d get updated to 3.0.xx. If I&#8217;m using 3.0.xx and check for updates, I don&#8217;t get updated. When the new release came out, I wasn&#8217;t sure if that meant that 3.0.xx users would get updated to 3.5.xx and 3.6.xx would need to be a manual update, or what? So the easy thing is just to go download it manually, since I was checking the website all day for the new version anyway.</p>
<p>3. About half of the boxes I use run Linux, where the Check for Updates thing is grayed out and if you want to run the current version of anything, it needs to be a manual install. So I manually download it from the website and put it in /opt/, since the repositories have an older version.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

