<br><br>
<div class="gmail_quote">On Thu, Mar 20, 2008 at 5:00 AM, Sitsofe Wheeler <<a href="mailto:sitsofe@yahoo.com">sitsofe@yahoo.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Many bugs reported turn out to be "hit and run" reports where something<br>is filed and never followed up. As such it is good that bugs are<br>
aggressively closed where possibly to prevent launchpad cluttering up.<br>Unfortunately there are scenarios where this becomes problematic.<br><br>These days I see people romping through launchpad asking for bugs to be<br>
retested on pre-releases of Ubuntu (which may be months away from their<br>final release). These bugs are stuffed into a Incomplete state and then<br>one month later closed (due to lack of response) before the final<br>release of Ubuntu is ever released. Sometimes these are bugs with very<br>
thorough descriptions which are reproducible all the time so there is<br>nothing stopping the launchpad gardener checking the problem.<br><br>A flip side of this is that sometimes a bug is reported and again at<br>some point before the next major release a request for testing is put<br>
out. The reporter goes away, tries the pre-release and tests the bug and<br>reports back. Then another request to test another pre-release comes up<br>because "maybe it's been fixed" but without any firm reason for this<br>
other than a minor point release change. Thus the bug is turned into a<br>game of how many pre-releases the reporter can keep up with.<br><br>The problem with all these requests for retesting is that the more bugs<br>someone files the more retests they will be asked to do thus punishing<br>
those who file real bugs that are not resolved. In order to keep<br><a href="http://bugs.launchpad.net/" target="_blank">bugs.launchpad.net</a> manageable perhaps collateral damage is inevitable<br>but if you are expecting people to be repeatedly testing things every<br>
month (or see their bug closed) then it would be nice if this was stated<br>up front.<br><br>--<br>Sitsofe | <a href="http://sucs.org/~sits/" target="_blank">http://sucs.org/~sits/</a><br><font color="#888888"><br><br><br>
--<br>Ubuntu-devel-discuss mailing list<br><a href="mailto:Ubuntu-devel-discuss@lists.ubuntu.com">Ubuntu-devel-discuss@lists.ubuntu.com</a><br>Modify settings or unsubscribe at: <a href="https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss" target="_blank">https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss</a><br>
</font></blockquote></div>
<div><br>Good morning,</div>
<div> </div>
<div>How would you suggest doing this instead? I am one of those that is combing launchpad for bugs that have not been reported or updated for a long time. I try to reproduce the bugs on my own system or vm which I try to run the development branch. If I am unable to reproduce it myself, I always ask the user to try and reproduce it as well.</div>
<div>So how would you suggest dealing with those bugs instead of asking the end user to deal with it?</div>
<div> </div>
<div>Jonathan</div>