[Dwn-trans-commit] CVS public_html/src/Writing/DWN

[CVS User joey]

Update of /var/cvs/infodrom.org/public_html/src/Writing/DWN
In directory finlandia:/home/users/joey/Projects/Web/public_html/src/Writing/DWN

Modified Files:
	dwn-2007-04.wml 
Log Message:
Polishing

--- /var/cvs/infodrom.org/public_html/src/Writing/DWN/dwn-2007-04.wml	2007/03/09 08:28:36	1.24
+++ /var/cvs/infodrom.org/public_html/src/Writing/DWN/dwn-2007-04.wml	2007/03/09 09:32:05	1.25
@@ -116,15 +116,15 @@
 potentially harmful and thus not encouraged.  He added implementation details
 and illustrated the events that lead to these restrictions.</p>
 
-<p><strong>Time before closing an unreproducible bug</strong>.  Julien Valroff
+<p><strong>Closing unreproducible Bugs.</strong>  Julien Valroff
 <a href="http://lists.debian.org/debian-mentors/2007/01/msg00565.html">\
-questioned</a> if there are any globally accepted consensus about when an
-unreproducible bug could be closed.  Neil Willians <a
+wondered</a> when a maintainer may close an unreproducible <a
+href="http://bugs.debian.org/396653">bug report</a>.  Neil Willians <a
 href="http://lists.debian.org/debian-mentors/2007/01/msg00568.html">added</a>
-a few general factors and itens to check before close it, and ended saying that
-<q>unreproducible has a similar meaning to moreinfo &ndash; it is open-ended
-and not suitable as a closure, particularly if the bug report indicates a
-crash</q>.</p>
+that it should be taken into account whether the submitter is responsive and
+whether the bug report includes sufficient information.  He asserted that the
+unreproducible tag has a similar meaning as moreinfo, i.e. the report should
+stay open, especially if it indicates a crash.</p>
 
 <p><strong>Want to continue reading DWN?</strong> Please help us create this
 newsletter.  We still need more volunteer writers who watch the Debian