<?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: On automatic bugreports</title>
	<atom:link href="http://blogs.gnome.org/alexl/2006/10/18/on-automatic-bugreports/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.gnome.org/alexl/2006/10/18/on-automatic-bugreports/</link>
	<description>Cool links and commentary</description>
	<lastBuildDate>Tue, 07 Feb 2012 16:04:15 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Christopher Blizzard</title>
		<link>http://blogs.gnome.org/alexl/2006/10/18/on-automatic-bugreports/comment-page-1/#comment-145</link>
		<dc:creator>Christopher Blizzard</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/alexl/2006/10/18/on-automatic-bugreports/#comment-145</guid>
		<description>I would like to point something out that we&#039;ve discovered from the Mozilla project.  That stacktraces are good for one thing: gathering statistics.  You know what your top crashers are and you fix them, driving the MTBF up.&lt;p/&gt;Every crash is probably a bug, but it&#039;s not worth the time to try and track down every crash with the time that you would apply to a well-diagnosed bug.  Instead treat it like it is: wisdom of the crowds, and use it to find the big stuff.  Or maybe the little stuff, too, but know that you will never be able to keep up with that much data.</description>
		<content:encoded><![CDATA[<p>I would like to point something out that we&#8217;ve discovered from the Mozilla project.  That stacktraces are good for one thing: gathering statistics.  You know what your top crashers are and you fix them, driving the MTBF up.
<p />Every crash is probably a bug, but it&#8217;s not worth the time to try and track down every crash with the time that you would apply to a well-diagnosed bug.  Instead treat it like it is: wisdom of the crowds, and use it to find the big stuff.  Or maybe the little stuff, too, but know that you will never be able to keep up with that much data.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- This Quick Cache file was built for (  blogs.gnome.org/alexl/2006/10/18/on-automatic-bugreports/feed/ ) in 1.18689 seconds, on Feb 12th, 2012 at 2:03 am UTC. -->
<!-- This Quick Cache file will automatically expire ( and be re-built automatically ) on Feb 12th, 2012 at 3:03 am UTC -->
