Please always read the CRAN policies first. This document gives some additional hints for a useful CRAN submission, especially for new submissions.
Unless there are good reasons, packages submitted to CRAN are expected
R CMD check --as-cran, and you will be asked to fix and
resubmit your package if it gives warnings or significant notes. To
avoid this, you should run
R CMD check --as-cran yourself with a
current development version of R before submitting to CRAN.
You can use the following web services to supplement your own tests:
In addition to the automated checks, we expect package authors to follow good practices that make their package more accessible and useful to the wider R community.
The most important way to do this is to write an informative entry in
Description field in the
DESCRIPTION file (see the
relevant section of the
R Extensions manual). The
are shown at the top of the CRAN landing page for the package, and
should therefore be written with care.
foo()but without quotes.
Sugihara (1994) <doi:10.1098/rsta.1994.0106>.
Srivastava et al. (2011) <arXiv:1103.3817>.
[email protected]field in DESCRIPTION giving all the authors, including contributors and copyright holders, with appropriate roles. For persons with an ORCID identifier (see https://orcid.org/ for more information, provide the identifier via an element named
person("Achim", "Zeileis", comment = c(ORCID = "0000-0003-0918-3766")).