Hi All,
Just thought that I would check to see if there are any known issues/delays for
CRAN in creating R release and devel binaries for Windows for updated packages.
It has been four days since I submitted an update and the other binaries were
created within a couple of days. The two Windows
Related to this:
It would be neat to have a dashboard that reports on the current
latency is on the different CRAN "queues" are, e.g. how long is the
average waiting time when submitting a new package ("newbies") until
you get a manual reply or it's on CRAN, submitting an update with all
OK
Thanks Martin,
I agree that the example should run for a user when calling example() - hence I
am going with a simple try() around the function calls in the examples. I agree
your more sophisticated version has better behaviour, but I don’t want to
clutter the examples with code that might
> Ben Bolker
> on Tue, 20 Oct 2020 17:07:10 -0400 writes:
> On 10/20/20 4:51 PM, Gábor Csárdi wrote:
>> On Tue, Oct 20, 2020 at 9:45 PM Ben Bolker wrote:
>> [...]
>>> if (testthat::skip_on_cran())
>>>
>>> all seem like reasonable solutions.
>>
>> I
