<?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: Of Bugs and Statuses</title>
	<atom:link href="http://blog.launchpad.net/general/of-bugs-and-statuses/feed" rel="self" type="application/rss+xml" />
	<link>http://blog.launchpad.net/general/of-bugs-and-statuses</link>
	<description>Thoughts from the Launchpad team</description>
	<lastBuildDate>Mon, 16 Nov 2009 11:43:14 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: solrize</title>
		<link>http://blog.launchpad.net/general/of-bugs-and-statuses/comment-page-1#comment-6410</link>
		<dc:creator>solrize</dc:creator>
		<pubDate>Mon, 07 Jul 2008 22:39:31 +0000</pubDate>
		<guid isPermaLink="false">http://news.launchpad.net/general/of-bugs-and-statuses#comment-6410</guid>
		<description>I saw &quot;triaged&quot; all the time but never understood what it meant.  What I&#039;m looking for is a way of closing a bug without either rejecting it or fixing it.  E.g. bug A is a genuine bug and discussion happens on its ticket.  Similarly with bug B, which is different from bug A.  I work on a fix that&#039;s primarily for bug B but is actually a unified fix for both bugs.  So I want to close bug A and refer viewers to bug B where discussion of the fix is taking place.  I don&#039;t want to mark A as duplicate since it&#039;s really a different bug and &quot;duplicate&quot; removes it from search (but there&#039;s still useful discussion there).  I don&#039;t want to mark it as &quot;fix committed&quot; because the fix is still in progress.  The idea is to merge two complex bugs and &quot;duplicate&quot; refers to a simpler situation where the same bug has gotten reported more than once.</description>
		<content:encoded><![CDATA[<p>I saw &#8220;triaged&#8221; all the time but never understood what it meant.  What I&#8217;m looking for is a way of closing a bug without either rejecting it or fixing it.  E.g. bug A is a genuine bug and discussion happens on its ticket.  Similarly with bug B, which is different from bug A.  I work on a fix that&#8217;s primarily for bug B but is actually a unified fix for both bugs.  So I want to close bug A and refer viewers to bug B where discussion of the fix is taking place.  I don&#8217;t want to mark A as duplicate since it&#8217;s really a different bug and &#8220;duplicate&#8221; removes it from search (but there&#8217;s still useful discussion there).  I don&#8217;t want to mark it as &#8220;fix committed&#8221; because the fix is still in progress.  The idea is to merge two complex bugs and &#8220;duplicate&#8221; refers to a simpler situation where the same bug has gotten reported more than once.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ralph Corderoy</title>
		<link>http://blog.launchpad.net/general/of-bugs-and-statuses/comment-page-1#comment-4934</link>
		<dc:creator>Ralph Corderoy</dc:creator>
		<pubDate>Fri, 04 Apr 2008 17:31:01 +0000</pubDate>
		<guid isPermaLink="false">http://news.launchpad.net/general/of-bugs-and-statuses#comment-4934</guid>
		<description>Could you please clarify who can set a bug to Confirmed?  The description says &quot;QA are meant to mark the bug confirmed only when they have enough information to reproduce the bug or trivially establish that it is in fact something that a developer needs to look at.&quot; but later it says &quot;community-confirmed bugs&quot; suggesting non-QA can confirm a bug.

And given the definition of Confirmed is &quot;Oh-Oh He’s Right It’s Broken&quot;, can a bug be set to that from the off because it&#039;s all too clear it&#039;s a bug.

https://bugs.launchpad.net/bugs/208837 is an example if you need a case in point.  :-)</description>
		<content:encoded><![CDATA[<p>Could you please clarify who can set a bug to Confirmed?  The description says &#8220;QA are meant to mark the bug confirmed only when they have enough information to reproduce the bug or trivially establish that it is in fact something that a developer needs to look at.&#8221; but later it says &#8220;community-confirmed bugs&#8221; suggesting non-QA can confirm a bug.</p>
<p>And given the definition of Confirmed is &#8220;Oh-Oh He’s Right It’s Broken&#8221;, can a bug be set to that from the off because it&#8217;s all too clear it&#8217;s a bug.</p>
<p><a href="https://bugs.launchpad.net/bugs/208837" rel="nofollow">https://bugs.launchpad.net/bugs/208837</a> is an example if you need a case in point.  <img src='http://blog.launchpad.net/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kiko</title>
		<link>http://blog.launchpad.net/general/of-bugs-and-statuses/comment-page-1#comment-3628</link>
		<dc:creator>kiko</dc:creator>
		<pubDate>Mon, 18 Feb 2008 19:04:46 +0000</pubDate>
		<guid isPermaLink="false">http://news.launchpad.net/general/of-bugs-and-statuses#comment-3628</guid>
		<description>It depends on what you mean by &quot;a bug is closed&quot;. If you mean the fix for the bug has been committed to revision control, use Fix Committed. If you mean that the fix for the bug is available to end-users, use Fix Released.

I guess that&#039;s ambiguous if you release to your end-users using revision control only, but which crazy project actually does that? &lt;wink&gt;</description>
		<content:encoded><![CDATA[<p>It depends on what you mean by &#8220;a bug is closed&#8221;. If you mean the fix for the bug has been committed to revision control, use Fix Committed. If you mean that the fix for the bug is available to end-users, use Fix Released.</p>
<p>I guess that&#8217;s ambiguous if you release to your end-users using revision control only, but which crazy project actually does that? <wink></wink></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel</title>
		<link>http://blog.launchpad.net/general/of-bugs-and-statuses/comment-page-1#comment-365</link>
		<dc:creator>Daniel</dc:creator>
		<pubDate>Sat, 24 Nov 2007 02:16:17 +0000</pubDate>
		<guid isPermaLink="false">http://news.launchpad.net/general/of-bugs-and-statuses#comment-365</guid>
		<description>I couldn&#039;t understand some parts of this article gs and Statuses at  Launchpad blog, but I guess I just need to check some more resources regarding this, because it sounds interesting.</description>
		<content:encoded><![CDATA[<p>I couldn&#8217;t understand some parts of this article gs and Statuses at  Launchpad blog, but I guess I just need to check some more resources regarding this, because it sounds interesting.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michal</title>
		<link>http://blog.launchpad.net/general/of-bugs-and-statuses/comment-page-1#comment-172</link>
		<dc:creator>Michal</dc:creator>
		<pubDate>Wed, 07 Nov 2007 21:10:59 +0000</pubDate>
		<guid isPermaLink="false">http://news.launchpad.net/general/of-bugs-and-statuses#comment-172</guid>
		<description>Once a bug is closed, what status do you use?  Does Fix Released mean closed?</description>
		<content:encoded><![CDATA[<p>Once a bug is closed, what status do you use?  Does Fix Released mean closed?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: santosh</title>
		<link>http://blog.launchpad.net/general/of-bugs-and-statuses/comment-page-1#comment-152</link>
		<dc:creator>santosh</dc:creator>
		<pubDate>Fri, 02 Nov 2007 21:15:08 +0000</pubDate>
		<guid isPermaLink="false">http://news.launchpad.net/general/of-bugs-and-statuses#comment-152</guid>
		<description>actually I wanted the clear life cycle of the bug in simple form.</description>
		<content:encoded><![CDATA[<p>actually I wanted the clear life cycle of the bug in simple form.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: b-initials</title>
		<link>http://blog.launchpad.net/general/of-bugs-and-statuses/comment-page-1#comment-118</link>
		<dc:creator>b-initials</dc:creator>
		<pubDate>Wed, 10 Oct 2007 09:40:24 +0000</pubDate>
		<guid isPermaLink="false">http://news.launchpad.net/general/of-bugs-and-statuses#comment-118</guid>
		<description>&lt;strong&gt;Bug statuses in&#160;Launchpad....&lt;/strong&gt;

I have been following the discussions on ubuntu-devel, -devel-discuss and -launchpad-users mailing lists regarding the status of Ubuntu bugs. There are many different discussion threads, some of them cross-posted, so it is a little difficult to give al...</description>
		<content:encoded><![CDATA[<p><strong>Bug statuses in&nbsp;Launchpad&#8230;.</strong></p>
<p>I have been following the discussions on ubuntu-devel, -devel-discuss and -launchpad-users mailing lists regarding the status of Ubuntu bugs. There are many different discussion threads, some of them cross-posted, so it is a little difficult to give al&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
