Release pacta.multi.loanbook 0.1.0

[jacobvjk]

First release

• usethis::use_news_md()
• usethis::use_cran_comments()
• Update (aspirational) install instructions in README
• Proofread Title: and Description:
• Check that all exported functions have @returns and @examples
• Check that Authors@R: includes a copyright holder (role ‘cph’)
• Check licensing of included files
• Review https://github.com/DavisVaughan/extrachecks

Prepare for release:

• git pull
• Check current CRAN check results
• Check if any deprecation processes should be advanced, as described in Gradual deprecation
• Polish NEWS
• urlchecker::url_check()
• devtools::build_readme()
• devtools::check(remote = TRUE, manual = TRUE)
• devtools::check_win_devel()
• revdepcheck::revdep_check(num_workers = 4)
• Update cran-comments.md
• git push
• Draft blog post

Submit to CRAN:

• usethis::use_version('minor')
• devtools::submit_cran()
• Approve email

Wait for CRAN...

• Accepted 🎉
• git push
• Finish & publish blog post
• Add link to blog post in pkgdown news menu
• usethis::use_github_release()
• usethis::use_dev_version(push = TRUE)
• Share on social media

[jacobvjk]

@jdhoffa It seems like it is not too common to have anything particular in the NEWS.md for the first CRAN submission. I checked some tidyverse examples and their NEWS tend to be populated starting with releases > 0.1.0.

[jdhoffa]

Ah indeed! NEWS should be empty.

The changelog starts after the package is on CRAN

[jacobvjk]

Ah indeed! NEWS should be empty.

The changelog starts after the package is on CRAN

which contradicts this to some degree: https://r-pkgs.org/release.html#sec-release-initial

Maybe we do this?

# pacta.multi.loanbook 0.1.0

* Initial CRAN submission.