New release and submit to CRAN (again)

[temospena]

I closed but forgot about this:

Fully agree with this, for v. 1.1 maybe.

Should we make a new release 1.1 and resubmit to CRAN?

Sure. I would say we can completely remove {raster}, don't bother with deprecating functions because the package has few users and it's already gone from CRAN, and then go for v.2.0.0 indicating breaking changes using SemVer conventions.

Originally posted by @temospena in #60

[temospena]

• update README
• update README figs
• check all vignetes
• update bootstrap
• fix or close existing issues
• new release with breaking changes
• submit to CRAN

[Robinlovelace]

Have you tried devtools::check_win()?

Can give it a go also..

[Robinlovelace]

Fired off devtools::check_win_devel(), check_win_release() and check_win_oldrelease(). Results should arrive via email to rob00x@gmail.com shortly — will report back once they come in.

[Robinlovelace]

Windows checks pass: https://win-builder.r-project.org/ec7sEwfSQmL3/00check.log

[Robinlovelace]

v1.2.0 submitted!

[temospena]

We are jumping the 1.1, but that should be ok!

[Robinlovelace]

Up to 10 days for manual review 🤞

[Robinlovelace]

Fixed!

[temospena]

We should create a new release (v2.0?)