<?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>shaver &#187; development</title>
	<atom:link href="http://shaver.off.net/diary/tag/development/feed/" rel="self" type="application/rss+xml" />
	<link>http://shaver.off.net/diary</link>
	<description>noise from signal</description>
	<lastBuildDate>Fri, 18 Nov 2011 02:15:21 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>why update add-ons now?</title>
		<link>http://shaver.off.net/diary/2008/01/24/why-update-add-ons-now/</link>
		<comments>http://shaver.off.net/diary/2008/01/24/why-update-add-ons-now/#comments</comments>
		<pubDate>Thu, 24 Jan 2008 14:47:13 +0000</pubDate>
		<dc:creator>shaver</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[development]]></category>
		<category><![CDATA[extensions]]></category>
		<category><![CDATA[firefox]]></category>
		<category><![CDATA[mozilla]]></category>

		<guid isPermaLink="false">http://shaver.off.net/diary/2008/01/24/why-update-add-ons-now/</guid>
		<description><![CDATA[With Firefox 3 still a couple of months away, it would seem reasonable to wonder why we&#8217;re encouraging add-on developers to get their add-ons updated for Firefox 3 already. For most add-on developers, it will indeed be a pretty quick process to update to the new chrome layout, a new API or two, and test [...]]]></description>
			<content:encoded><![CDATA[<p>With Firefox 3 still a couple of months away, it would seem reasonable to wonder why we&#8217;re <a href="http://starkravingfinkle.org/blog/2008/01/extension-developers-more-on-updating/">encouraging add-on developers</a> to get their <a href="http://developer.mozilla.org/en/docs/Updating_extensions_for_Firefox_3">add-ons updated for Firefox 3</a> already.  For most add-on developers, it will indeed be a pretty quick process to update to the new chrome layout, a new API or two, and test it out, but we want people to start on that process now nonetheless.  There are two reasons for this, in my mind:</p>

<ul>
<li> The kinds of people who <a href="http://www.mozilla.com/en-US/firefox/3.0b2/whatsnew/">test our betas</a> and give us great feedback are the kinds of people who have a bunch of extensions installed, and not having their favourite extensions work makes it much less pleasant for them to do in-depth testing.</li>
<li> If there <i>is</i> a hard problem found when updating an add-on, we want to know about things we can do on the Firefox side to make it easier, in time for those changes to safely get into the release stream.  Waiting until the Firefox <abbr title="release candidate">RC</abbr>s are out would mean that we have a lot, <i>lot</i> less room to maneuver when it comes to resolving any problems found.</li>
</ul>

<p>So please, take a moment to start updating your add-on this weekend, and <a href="http://groups.google.com/group/mozilla.dev.extensions/topics">let us know</a> if you need help.  Operators, in the Special Forces sense, are standing by.</p>
]]></content:encoded>
			<wfw:commentRss>http://shaver.off.net/diary/2008/01/24/why-update-add-ons-now/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
	</channel>
</rss>

