Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

httpuv v1.6.11 release checklist #371

Closed
15 of 16 tasks
jcheng5 opened this issue May 11, 2023 · 1 comment
Closed
15 of 16 tasks

httpuv v1.6.11 release checklist #371

jcheng5 opened this issue May 11, 2023 · 1 comment

Comments

@jcheng5
Copy link
Member

jcheng5 commented May 11, 2023

  • If not a new package, make sure any warnings/errors in CRAN check results page are fixed
  • Build and check on Centos 7
  • Build and check with debug builds of R (RDcsan, RDsan)
  • Create RC branch rc-v1.6.11
  • Change the DESCRIPTION and NEWS on this branch to change the version number to the desired version for CRAN
  • Perform Shiny final test pass on rc-v1.6.11
  • Clean your package directory to remove any extraneous files, including ones that are git-ignored. (Warning, this will delete any unsaved buffers in RStudio! Also, be sure to close RStudio before taking this step!) git clean -xdi .
  • Build your package. I (jcheng) personally do it from the Mac command line like this:
    PATH=$PATH:/Applications/RStudio.app/Contents/MacOS/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 R CMD check --as-cran pkg_version.tar.gz both locally and on win-builder. You can also use https://r-hub.github.io/rhub/.
  • Review CRAN Policies document
  • Submit to CRAN via their online form.
  • When accepted, tag the RC branch with a v1.6.11 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.6.11.9000.
@jcheng5 jcheng5 mentioned this issue May 11, 2023
7 tasks
@jcheng5 jcheng5 closed this as completed May 12, 2023
@wch
Copy link
Collaborator

wch commented May 12, 2023

For future releases, this checklist should also have an item for making a GitHub release for the tag.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants