blog post: how to keep up with CRAN

[maelle]

Official communication channels

• CRAN policy, with the watch services by Dirk Eddelbuettel

  • mirror https://github.com/eddelbuettel/crp
  • Twitter account https://twitter.com/CRANPolicyWatch

• R Journal (use bib2df to parse the general .bib, show that there's a recurrent article "Changes on CRAN"). These articles have info about policy changes but also changes in the submission pipelines, check setups etc.

Other information sources

• Your own packages, link to our post about CRAN checks, in particular the section about noticing their changes.

• Only using an up-to-date email address as maintainer!

• R-package-devel and other venues where folks ask for R package development help, because they will mention CRAN stuff. R-package-devel more than other venues because users know CRAN "listens" to that list.

[maelle]

About the why

• as maintainer you need to know what to expect for your packages currently on CRAN and your future submissions.
• as the provider of tools for R package developers, like R-hub, you need to know how to tweak your tool. Remind how to get in touch with R-hub. Link to the post about noLD + the post about CRAN checks.

[maelle]

dirk.eddelbuettel.com/blog/2013/10/23/

https://recology.info/2015/02/package-dev/#cran-policy-changes (and therefore mention my own post about keeping up-to-date with R news https://masalmon.eu/2019/01/25/uptodate/)