Release ColOpenData 0.3.0

[jd-otero]

First release:

• usethis::use_cran_comments()
• Update (aspirational) install instructions in README
• Proofread Title: and Description:
• Check that all exported functions have @return 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
• urlchecker::url_check()
• devtools::build_readme()
• devtools::check(remote = TRUE, manual = TRUE)
• devtools::check_win_devel()
• git push
• Draft blog post
• Run goodpractice::gp()
• Review WORDLIST
• Check if # nolint comments are still needed with recent lintr releases
• All contributors to this release are acknowledged in some way

Submit to CRAN:

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

Wait for CRAN...

• Accepted 🎉
• 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

[jd-otero]

Since CRAN submissions are suspended from august 1st to august 16th, the submission will have to wait until august 17th

[macataci]

We just submitted to CRAN! Let's hope it will not present any problem.

[Bisaloo]

Hi @jd-otero @macataci, I notice that version 0.3.0 and 0.3.1 were not tagged on GitHub.

usethis::use_github_release() should take care of this using the commit id stored in the CRAN-RELEASE file, but it looks like something went wrong somewhere.

Do you still have the CRAN-RELEASE file?

If not, I can identify the commit used for the release and tag a GitHub release myself using it for this time. Please let me know what would be best for you.