[R-pkg-devel] Is S3 class registration essential for CRAN?

[Dirk Eddelbuettel]

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 submission by registering all S3 methods, needs to be fixed for _some_, or doesn't need to be changed (the present version on cran is running without apparent issues, but was submitted before the checks expanded to pick this up).

You are expected to test with the release and the development versions of R
[1], and newer versions tend to only get stricter rather than more lenient.

As for 'current version on CRAN does not have issues': well, yes, the absence
of a time machine comes into play again. Tests that didn't exist at the time
have a tendency to not get triggered.  Rest assurred that the _next_ upload
will however so you are quite right to worry about this.

So without knowing the pecularities of your (unnamed) package: I'd fix it.

Dirk


[1] Using win-builder can be a good trick to get access at the latter.

-- 
http://dirk.eddelbuettel.com | @eddelbuettel | edd at debian.org