From dmurdoch at pair.com  Mon Jan 19 15:12:42 2004
From: dmurdoch at pair.com (Duncan Murdoch)
Date: Mon Jan 19 15:11:00 2004
Subject: [Rd] Wish list
In-Reply-To: <20040119075134.163cf1d8.feh3k@spamcop.net>
References: <20040117093310.29ee370a.feh3k@spamcop.net>
	<jm6m00hgtuffsdcv972elvv4vjh18kv68b@4ax.com>
	<20040119075134.163cf1d8.feh3k@spamcop.net>
Message-ID: <e4pn00tgv2hqn18rbebdvn2c6rv4abjdv4@4ax.com>

On Mon, 19 Jan 2004 07:51:34 -0500, Frank E Harrell Jr
<feh3k@spamcop.net> wrote :

>On Sun, 18 Jan 2004 18:47:52 -0500
>Duncan Murdoch <dmurdoch@pair.com> wrote:

>> Changes always show up in r-devel (the main CVS branch, not the
>> mailing list) first.  Package developers should be keeping a
>> relatively up to date copy of it around if they're doing things that
>> are likely to break.
>
>I need to do that more often.  But sometimes it's hard to know what things
>I do that are likely to break.  That's where there needs to be some other
>mechanism for user communications.

Generally when people know something is likely to cause trouble,
there's a posting to this mailing list  ---  but it's easy to overlook
it among all the other traffic.

To make it a bit easier for Windows package developers to test against
r-devel, I'm going to keep a reasonably up-to-date Windows build
online.  For now it's on CRAN, but there are concerns about the impact
on the mirrors of the extra file size and download traffic.  However,
if I have to move it the links on CRAN will be updated, so it's safe
to say you should start looking at
<http://cran.r-project.org/bin/windows/base>.

Duncan Murdoch


[Rd] Wish list
Duncan Murdoch