Release dbplyr 2.3.0

[hadley]

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::cloud_check()
  • https://github.com/bcgov/bcdata — Failure with released bcdata and dev dbplyr bcgov/bcdata#304
  • https://github.com/data-cleaning/dcmodifydb — Failure with released dcmodifydb and dev dbplyr data-cleaning/dcmodifydb#12
  • https://github.com/data-cleaning/validatedb — Failure with released validatedb and dev dbplyr data-cleaning/validatedb#7
• Update cran-comments.md
• git push
• Draft blog post — dbplyr 2.3.0 tidyverse.org#613
• Slack link to draft blog in #open-source-comms
• Wait until Jan 16

Submit to CRAN:

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

Wait for CRAN...

• Accepted 🎉
• git push
• usethis::use_github_release()
• usethis::use_dev_version()
• git push
• Finish blog post
• Tweet
• Add link to blog post in pkgdown news menu

[hadley]

@mgirlich anything else you want in this release? I figure #1074 can wait for another release soon after dplyr 1.1.0 is out.

[hadley]

Revdep failure all look related to stricter handling of absent variables; I'll try and take a closer look tomorrow.

[mgirlich]

@mgirlich anything else you want in this release? I figure #1074 can wait for another release soon after dplyr 1.1.0 is out.

I don't need anything else in this release and I agree that #1074 can wait.

[hadley]

Let's schedule this for Jan 16 — I'd normally only give dcmodifydb and validatedb another week or two since we notified them in September, it feels unkind to give a short deadline at this time of year.