Chapter 7 Preparing and Submitting to CRAN

7.1 A Checklist for pre-CRAN submission

Before submitting to CRAN, file an issue on your package with the following checklist. Fill it out as you go along with the preparation to submit steps outlined below.

- [ ] Update the README.Rmd and re-knit

- [ ] Update the package site

- [ ] Update the package vignette, if you have one

- [ ] Update the package NEWS.md

- [ ] Make sure you pass build check

- [ ] Check your package with styler

- [ ] Check your package with goodpractice::gp()

- [ ] Run devtools checks and make sure you pass

- [ ] Update the package cran-comments.md

- [ ] Submit to CRAN with devtools::release()

7.2 Guidance on executing your checklist.

Before submitting to CRAN, we’d ask that you

1. Make sure you pass build check (Check in the RMarkdown Build tab) with no errors, no warnings, no notes.

2. Update any vignettes with basic examples, the NEWS.md file with what is being released (or any changes from previous versions), and the README.Rmd with any final details.

3. Build a pkgdown website to help users. Make sure to link to it in your github repo.

# make a pkgdown website!
pkgdown::build_site()

4. Check your code to make sure it is is easy to read and well styled. This can be done easily with the styler package.

styler::style_pkg()

5. Take a final check through to make sure your package is obeying best-practices using the goodpractice library.

goodpractice::gp()

6. Execute final checks. First, make sure after making revisions from the above, you pass Build Check again. Then, walk through the following final checks provided by devtools.

# for release - checks!
devtools::check_win_release()
devtools::release_checks()
devtools::spell_check()
devtools::check_rhub()

7. Release! Again, using devtools (which will check you)!

#-------------
# Release ####
#-------------
devtools::release()