<?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/"
	xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"
	>
<channel>
	<title>Comments on: The new amateuristic release strategy of Firefox</title>
	<atom:link href="http://www.g-loaded.eu/2011/09/28/the-new-amateuristic-release-strategy-of-firefox/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.g-loaded.eu/2011/09/28/the-new-amateuristic-release-strategy-of-firefox/</link>
	<description>An open-source software and technology related journal</description>
	<lastBuildDate>Tue, 18 Jun 2013 13:13:01 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Abercrombie</title>
		<link>http://www.g-loaded.eu/2011/09/28/the-new-amateuristic-release-strategy-of-firefox/#comment-19268</link>
		<dc:creator>Abercrombie</dc:creator>
		<pubDate>Sat, 14 Jan 2012 05:33:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.g-loaded.eu/?p=2505#comment-19268</guid>
		<description><![CDATA[I don&#039;t advocate with IE and firefox. I usually use a web browser to complete the various tasks. Without any reason is invalid, proved to be the is a waste of time, deal with extended because the new version not compatible with strategy.]]></description>
		<content:encoded><![CDATA[<p>I don&#8217;t advocate with IE and firefox. I usually use a web browser to complete the various tasks. Without any reason is invalid, proved to be the is a waste of time, deal with extended because the new version not compatible with strategy.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stunt</title>
		<link>http://www.g-loaded.eu/2011/09/28/the-new-amateuristic-release-strategy-of-firefox/#comment-19265</link>
		<dc:creator>Stunt</dc:creator>
		<pubDate>Thu, 05 Jan 2012 21:25:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.g-loaded.eu/?p=2505#comment-19265</guid>
		<description><![CDATA[Like you I&#039;ve been with FF since Phoenix days.

The whole Firefox/Thunderbird release strategy is a joke.  Some addons disable every time, and most of the time reading the release notes they&#039;ve barely added anything - so who does it benefit.

Chrome can manage to update dozens of times and never once have I noticed, cared or has an addon broken.  So they should take a leaf out of G&#039;s book and only enable the crazy &quot;but it goes upto 11&quot; updating scheme only when they&#039;ve figured out how to a) Do it entirely invisibly, and b) Never break an addon.

Whilst I&#039;m whinging why, oh why, does TB now include a full blown instance of FF browser, complete with plugins and addons.  I know I need to process HTML emails, but really just use the basic engine - with no extra junk.  Isn&#039;t the bloat of Communicator what prompted the separation in the first place, with an aim to have superfluous stuff in addons?]]></description>
		<content:encoded><![CDATA[<p>Like you I&#8217;ve been with FF since Phoenix days.</p>
<p>The whole Firefox/Thunderbird release strategy is a joke.  Some addons disable every time, and most of the time reading the release notes they&#8217;ve barely added anything &#8211; so who does it benefit.</p>
<p>Chrome can manage to update dozens of times and never once have I noticed, cared or has an addon broken.  So they should take a leaf out of G&#8217;s book and only enable the crazy &#8220;but it goes upto 11&#8243; updating scheme only when they&#8217;ve figured out how to a) Do it entirely invisibly, and b) Never break an addon.</p>
<p>Whilst I&#8217;m whinging why, oh why, does TB now include a full blown instance of FF browser, complete with plugins and addons.  I know I need to process HTML emails, but really just use the basic engine &#8211; with no extra junk.  Isn&#8217;t the bloat of Communicator what prompted the separation in the first place, with an aim to have superfluous stuff in addons?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: I also remember Phoenix</title>
		<link>http://www.g-loaded.eu/2011/09/28/the-new-amateuristic-release-strategy-of-firefox/#comment-19116</link>
		<dc:creator>I also remember Phoenix</dc:creator>
		<pubDate>Wed, 09 Nov 2011 16:41:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.g-loaded.eu/?p=2505#comment-19116</guid>
		<description><![CDATA[There&#039;s something to be said for allowing your users to choose! Look at Ubuntu. They&#039;ve fixed the worst aspect of Debian (*long* release cycles) and they deliver releases every six months. However, they also create LTS (long term support) releases for customers (e.g. enterprise) who don&#039;t want to be on a release treadmill.

If Mozilla wants to push out new releases more frequently, it would really be nice if they could commit to patching security holes in a given release (&quot;LTS&quot;) so that users and extension developers have a stable platform to rely on. Those that want bleeding edge features can jump on the release treadmill.

Instead what they&#039;ve effectively done is forced users into testing beta releases, even though they&#039;re not called that.]]></description>
		<content:encoded><![CDATA[<p>There&#8217;s something to be said for allowing your users to choose! Look at Ubuntu. They&#8217;ve fixed the worst aspect of Debian (*long* release cycles) and they deliver releases every six months. However, they also create LTS (long term support) releases for customers (e.g. enterprise) who don&#8217;t want to be on a release treadmill.</p>
<p>If Mozilla wants to push out new releases more frequently, it would really be nice if they could commit to patching security holes in a given release (&#8220;LTS&#8221;) so that users and extension developers have a stable platform to rely on. Those that want bleeding edge features can jump on the release treadmill.</p>
<p>Instead what they&#8217;ve effectively done is forced users into testing beta releases, even though they&#8217;re not called that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chuck Jones</title>
		<link>http://www.g-loaded.eu/2011/09/28/the-new-amateuristic-release-strategy-of-firefox/#comment-19010</link>
		<dc:creator>Chuck Jones</dc:creator>
		<pubDate>Mon, 17 Oct 2011 01:26:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.g-loaded.eu/?p=2505#comment-19010</guid>
		<description><![CDATA[Seriously Mozilla, let&#039;s ease off on the updates. Every day my wife complains that she has to update *AGAIN* just to be able to surf the web. I turned off auto updates to stop her complaining. I downgraded to 3.6 as my favorite password automator isn&#039;t interested in running with the bulls and neither am I ...]]></description>
		<content:encoded><![CDATA[<p>Seriously Mozilla, let&#8217;s ease off on the updates. Every day my wife complains that she has to update *AGAIN* just to be able to surf the web. I turned off auto updates to stop her complaining. I downgraded to 3.6 as my favorite password automator isn&#8217;t interested in running with the bulls and neither am I &#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: George Notaras</title>
		<link>http://www.g-loaded.eu/2011/09/28/the-new-amateuristic-release-strategy-of-firefox/#comment-19000</link>
		<dc:creator>George Notaras</dc:creator>
		<pubDate>Thu, 13 Oct 2011 20:41:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.g-loaded.eu/?p=2505#comment-19000</guid>
		<description><![CDATA[@kazetsukai: I didn&#039;t say I prefer IE over Firefox. What I really said is that, if Firefox upgrades continue to give me a hard time with the extensions I use, I wouldn&#039;t mind switching to another web browser that lets me do my job uninterrupted, even a closed-source one like IE. I use the web browser to accomplish various tasks. There is no reason valid enough to justify the time that is wasted while dealing with extension incompatibilities because of the new release strategy. I&#039;m sure the enterprise world won&#039;t approve this new release strategy.]]></description>
		<content:encoded><![CDATA[<p>@kazetsukai: I didn&#8217;t say I prefer IE over Firefox. What I really said is that, if Firefox upgrades continue to give me a hard time with the extensions I use, I wouldn&#8217;t mind switching to another web browser that lets me do my job uninterrupted, even a closed-source one like IE. I use the web browser to accomplish various tasks. There is no reason valid enough to justify the time that is wasted while dealing with extension incompatibilities because of the new release strategy. I&#8217;m sure the enterprise world won&#8217;t approve this new release strategy.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kazetsukai</title>
		<link>http://www.g-loaded.eu/2011/09/28/the-new-amateuristic-release-strategy-of-firefox/#comment-18999</link>
		<dc:creator>kazetsukai</dc:creator>
		<pubDate>Thu, 13 Oct 2011 20:15:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.g-loaded.eu/?p=2505#comment-18999</guid>
		<description><![CDATA[Like Firefox or not... if you prefer IE to anything, you&#039;re crazy.]]></description>
		<content:encoded><![CDATA[<p>Like Firefox or not&#8230; if you prefer IE to anything, you&#8217;re crazy.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: George Notaras</title>
		<link>http://www.g-loaded.eu/2011/09/28/the-new-amateuristic-release-strategy-of-firefox/#comment-18951</link>
		<dc:creator>George Notaras</dc:creator>
		<pubDate>Thu, 29 Sep 2011 20:43:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.g-loaded.eu/?p=2505#comment-18951</guid>
		<description><![CDATA[All I say is that they rushed to switch to the new release strategy without first making sure that the transition would be smooth for the users. Hence the &lt;em&gt;amateuristic&lt;/em&gt;. Why the rush? Jetpack should be used for a while (&gt; year), so as to give extension developers enough time to adopt it. After the major extension developers had switched, then they could change the release strategy. But, in this case, marketing was the real reason for the rush to switch strategies. There is no other explanation that makes sense...]]></description>
		<content:encoded><![CDATA[<p>All I say is that they rushed to switch to the new release strategy without first making sure that the transition would be smooth for the users. Hence the <em>amateuristic</em>. Why the rush? Jetpack should be used for a while (&gt; year), so as to give extension developers enough time to adopt it. After the major extension developers had switched, then they could change the release strategy. But, in this case, marketing was the real reason for the rush to switch strategies. There is no other explanation that makes sense&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: comzeradd</title>
		<link>http://www.g-loaded.eu/2011/09/28/the-new-amateuristic-release-strategy-of-firefox/#comment-18949</link>
		<dc:creator>comzeradd</dc:creator>
		<pubDate>Wed, 28 Sep 2011 17:03:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.g-loaded.eu/?p=2505#comment-18949</guid>
		<description><![CDATA[You are actually wrong on everything :)

The new release strategy is an engineering decision, not a marketing one. It&#039;s a way to adopt more rapidly new features. (Remember how long we&#039;ve been waiting for the FF4).
See &lt;a href=&quot;https://wiki.mozilla.org/Features/Release_Tracking&quot; rel=&quot;nofollow&quot;&gt;here&lt;/a&gt; a list of features and technologies that users will experience in the near future, just because of the new release strategy.

As for the extensions thing... well it was time for a breakthrough and it was inevitable to break backwards compatibility. From now on all add-on developers should use &lt;a href=&quot;https://addons.mozilla.org/en-US/developers/builder&quot; rel=&quot;nofollow&quot;&gt;Jetpack&lt;/a&gt;, so their extensions keep running regardless of the FF version ;)]]></description>
		<content:encoded><![CDATA[<p>You are actually wrong on everything :)</p>
<p>The new release strategy is an engineering decision, not a marketing one. It&#8217;s a way to adopt more rapidly new features. (Remember how long we&#8217;ve been waiting for the FF4).<br />
See <a href="https://wiki.mozilla.org/Features/Release_Tracking" rel="nofollow">here</a> a list of features and technologies that users will experience in the near future, just because of the new release strategy.</p>
<p>As for the extensions thing&#8230; well it was time for a breakthrough and it was inevitable to break backwards compatibility. From now on all add-on developers should use <a href="https://addons.mozilla.org/en-US/developers/builder" rel="nofollow">Jetpack</a>, so their extensions keep running regardless of the FF version ;)</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk: basic
Page Caching using disk: enhanced
Object Caching 227/229 objects using apc

Served from: www.g-loaded.eu @ 2013-06-19 07:15:42 -->