From murdoch@stats.uwo.ca  Thu Oct  4 00:23:29 2001
From: murdoch@stats.uwo.ca (murdoch@stats.uwo.ca)
Date: Thu, 4 Oct 2001 01:23:29 +0200 (MET DST)
Subject: [Rd] bug.report() & docs should mention r-devel (PR#1113)
Message-ID: <200110032323.BAA11124@pubhealth.ku.dk>

Full_Name: Duncan Murdoch
Version: 1.3.1
OS: Windows
Submission from: (NULL) (64.231.172.71)


None of the web page on bug tracking, the ?bug.report help page, 
nor the disclaimer inserted at the beginning of the text generated by bug.report
in Windows mention
 - that only one bug should go in each report
 - that it's a good idea to discuss things on r-devel if you're not sure
something
is a bug.

I'd add this to the bug.report disclaimer:

"If you are not sure if what you see is a bug, please discuss it on the r-devel

mailing list first.  If you are sure, please copy the bug report 
(after finishing it) to your favorite email program and send it to
<address>.  Please submit just one bug per message."

The other places could have more verbose versions of this advice, including 
advice not to cc it to other lists.

 

-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-
r-devel mailing list -- Read http://www.ci.tuwien.ac.at/~hornik/R/R-FAQ.html
Send "info", "help", or "[un]subscribe"
(in the "body", not the subject !)  To: r-devel-request@stat.math.ethz.ch
_._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._


[Rd] bug.report() & docs should mention r-devel (PR#1113)
murdoch@stats.uwo.ca