Release argoFloats 1.0.7

[dankelley]

Prepare for release:

• [x] git pull
• [x] Check current CRAN check results
• [x] Polish NEWS
• [x] urlchecker::url_check()
• ~devtools::build_readme()~ I do this manually.
• [x] devtools::check(remote = TRUE, manual = TRUE)
• [x] devtools::check_win_devel()
• [x] revdepcheck::revdep_check(num_workers = 4)
• [x] Update cran-comments.md
• [x] git push

Submit to CRAN:

• ~usethis::use_version('patch')~ I do this manually
• [x] devtools::submit_cran()
• [x] Approve email

Wait for CRAN...

• [x] Accepted :tada:
• [x] usethis::use_github_release()
• ~usethis::use_dev_version(push = TRUE)~ I do this manually

[dankelley]

An initial hurdle has been passed, as evidenced by the following quote from an email I just received.

Dear maintainer,

thanks, package argoFloats_1.0.7.tar.gz is on its way to CRAN.

Best regards, CRAN teams' auto-check service Flavor: r-devel-linux-x86_64-debian-gcc, r-devel-windows-x86_64 Check: CRAN incoming feasibility, Result: Note_to_CRAN_maintainers Maintainer: 'Dan Kelley [dan.kelley@dal.ca](mailto:dan.kelley@dal.ca)'

[dankelley]

It's making its way through the CRAN process. Several pre-built binaries are now available on CRAN, and about half the testing machines have assessed it. Importantly, one of the test machines that previously had the problem of suggesting rgdal now passes the code cleanly.

I would be surprised to see problems in the other machines, but I will leave this issue (and its sibling, #597) open until the new version is available in binary form for all platforms, and has tested cleanly on all platfroms.

[dankelley]

This is now available in binary form for all the platforms supported by CRAN, and has built on all test platforms except r-devel-linux-x86_64-debian-clang and r-release-linux-x86_64. When it clears on those last platforms, I will close this issue.

[dankelley]

All the remote checks at https://cran.r-project.org/web/checks/check_results_argoFloats.html have now been done for this version, so I am closing the issue.

A note for future planning: it took 5 days for one of the remote-check machines to do the update.