colearendt / tidyjson

Tidy your JSON data in R with tidyjson
Other
184 stars 15 forks source link

CRAN Release 0.3.2 #143

Closed colearendt closed 1 year ago

colearendt commented 1 year ago

Related to #142

on RStudio Cloud / RSP

PATH=$PATH:/usr/lib/rstudio-server/bin/pandoc/pandoc R CMD build [pkgdir]

- [ ] Do a sanity check by installing/testing the built package.
- [ ] Perform revdep check using https://github.com/r-lib/revdepcheck, if this is not the initial CRAN release.
- [ ] Run the following both locally and on [win-builder](https://win-builder.r-project.org/upload.aspx). You can also use https://r-hub.github.io/rhub/.

PATH=$PATH:/Applications/RStudio.app/Contents/MacOS/pandoc R CMD check --as-cran pkg_version.tar.gz

on RStudio Cloud / RSP

PATH=$PATH:/usr/lib/rstudio-server/bin/pandoc/pandoc R CMD check --as-cran pkg_version.tar.gz

- [ ] I don't know how much it matters but I have this file as my ~/.R/Makevars:

CFLAGS += -Wall -pipe -pedantic -std=gnu99 -g -O0 CXXFLAGS += -Wall -pipe -Wno-unused -pedantic -g -O0 CXX11FLAGS += -Wall -pipe -Wno-unused -pedantic -g -O0


- [ ] Read every bullet point in the CRAN Policies document if this is the first release of the package. I usually print it out and check off the items one by one.
- [ ] [Submit to CRAN via their online form](https://cran.r-project.org/submit.html).
- [ ] If there are R CMD check warnings that are unavoidable, make sure to explain them in the comments.
- [ ] If rejected, make changes on the RC branch and bump the fourth (patch) version component, i.e. 1.5.2.1.
- [ ] When accepted, tag the RC branch with a v1.5.2.1 tag (or whatever version you finally ended up getting accepted), and push the tag to origin.
- [ ] Merge RC into master.
- [ ] On master, change the package version to 1.5.2.9000.