Skip to content
Prev 69 / 703 Next

R-bugs interfacing to R-devel mailing list

I've been hacking at the JitterBug sources a little, so that it should
work better with mailing lists. It has been running with the core team
list for a while and seems to be OK.

I will now move the forwarding address to the r-devel list where it
really belongs. I hope this will make it easier for people outside the
core team to contribute to the development of R by participating in
the discussions and helping to analyse bug reports.

Points to note:

All entries (web or email) to R-bugs are echoed to R-devel, *except*
those marked "private" on the web form, and/or containing the word
PRIVATE (in uppercase) in the subject field.

The Reports arrive at R-devel with R-bugs in the Cc: field, so if you
reply to "sender and all recipients" (AKA "wide reply") the reply gets
registered as a followup in R-bugs. There is code in Jitterbug to
prevent the autoforwarding of messages which have already been copied
to R-devel, but note that if the original sender also reads R-devel,
he or she will still get the reply twice, so you may still need to
edit the headers.

Please do *not* Cc: bug reports to other lists. This will only cause
most people to receive it in two versions, one of which will be
lacking the Problem Report identifier (PR# xxx). If someone then
replies to "all recipients", this will open up a *new* Problem Report,
etc.