Release PROJ 0.4.5

[mdsumner]

Heck, none of this is working atm I thought I made progress but keep getting it wrong...

Re-establish the mode where if PROJ 6 is not available the package isn't functional. That means ifdefs around each C function, and return NULL for each. This means the package builds and installs no matter what version of PROJ is or isn't available, and reproj can then fall back to using proj4 package (this might not be the best way to do it now, it just was beyond my ability originally).

in a dev branch

• establish ifdefs for harmless no-func
• ensure tests work on pre-6.3.1
• ensure the mocking works for testing
• check the docs etc.

• Milestones https://github.com/hypertidy/PROJ/issues?q=is%3Aopen+is%3Aissue+milestone%3A0.5.0
• increase test coverage
• sort out Dockerfile/s
• check valgrind
• check clang
• pass all on github
• pass macbuilder
• pass win-devel
• pass win-release

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
• devtools::build_readme()
• urlchecker::url_check()
• devtools::check(remote = TRUE, manual = TRUE)
• devtools::check_win_devel()
• rhub::check_for_cran()
• rhub::check(platform = 'ubuntu-rchk')
• rhub::check_with_sanitizers()
• 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
• usethis::use_github_release()
• usethis::use_dev_version()
• git push
• Finish blog post
• Tweet
• Add link to blog post in pkgdown news menu

[mdsumner]

it's done