I second Dirk. Also, from my experience:
A good rule of thumb is that you should fix all NOTEs (i.e. not have
them) when you submit to CRAN. It's only when you have a really good
reason you could try to convince CRAN that they are there and that
they cannot be fixed easily. I've got 20+
On 12 July 2016 at 17:47, S Ellison wrote:
| A short question: How necessary is explicit S3 class registration for CRAN
submission?
| R-forge's check is giving me a note on this for a handful of methods in a
package, and I'm unclear whether it is something that _needs_ to be fixed for
CRAN
A short question: How necessary is explicit S3 class registration for CRAN
submission?
R-forge's check is giving me a note on this for a handful of methods in a
package, and I'm unclear whether it is something that _needs_ to be fixed for
CRAN submission by registering all S3 methods, needs
