Prepare for CRAN submission

[trashbirdecology]

Prepare for release:

• Check that description is informative
  • Add relevant copyrights to libraries used (e.g. dplyr, magrittr, etc [see imports and depends in DESCRIPTION.md]) (this was a task added by JLB)
  • Add relevant copyrights to the licensing (this was a task added by JLB)
• [x ] Check licensing of included files
  • make sure we incorporate the necessary copy rights or licenses from rBBS (CC0)
  • make sure we incorporate the necessary copy rights or licenses for the N.Amer BBS (CC0)
• usethis::use_cran_comments()
• devtools::check()
  • address all issues appearing in the checks (e.g. failures; no visible bindings; malformed descri. fields) (@GabsPalomo)
• devtools::check_win_devel()
• [] create package website (added by JLB ) see here for details
• Polish pkgdown reference index
• Draft blog post

Submit to CRAN:

• usethis::use_version('major')
• Update cran-comments.md
• devtools::submit_cran()
• Approve email

Wait for CRAN...

• Accepted 🎉
• usethis::use_github_release()
• usethis::use_dev_version()
• Update install instructions in README
• Finish blog post
• Tweet
• Add link to blog post in pkgdown news menu

[atyre2]

Have you considered getting this onboarded with rOpenSci? either before or after CRAN submission.

[trashbirdecology]

No, but that's a great idea...would be a good excuse to redo the function naming convention to object_verb (currently is verb_objObj).