[R-pkg-devel] puzzling CRAN rejection

[Ben Bolker]

On 10/12/20 6:36 PM, Duncan Murdoch wrote:
> On 12/10/2020 6:14 p.m., Ben Bolker wrote:
>>
>>
>>>
>>> I'd say a mismatch in saved output isn't a small problem, it's either a
>>> too-sensitive test or something serious.
>>>
>>> Duncan Murdoch
>>>
>>
>>     That's fair enough, but it would be nice if (1) this were a NOTE and
> 
> I don't think so.  As I said, I think it should be marked as an ERROR.

   OK.  But it would probably be wise (if the CRAN maintainers actually 
wanted to do this) to crank it up from silent -> NOTE -> WARNING -> 
ERROR over the course of several releases so as not to have widespread 
test failures on CRAN right away ...


> 
> Duncan Murdoch
> 
>> (2) it were made explicit in the CRAN policy that, *except by special
>> exception*, an unresolved NOTE is grounds for rejection.  This is
>> broadly understood by experienced package maintainers but must sometimes
>> come as a shock to newbies ...
> 
>