thisisnic opened a new issue, #36733: URL: https://github.com/apache/arrow/issues/36733
### Describe the bug, including details regarding any error messages, version, and platform. # Packaging checklist for CRAN release ## Before the release candidate is cut - [ ] [Create a GitHub issue](https://github.com/apache/arrow/issues/new/) entitled `[R] CRAN packaging checklist for version X.X.X` and copy this checklist to the issue. - [ ] Evaluate the status of any failing [nightly tests and nightly packaging builds](http://crossbow.voltrondata.com). These checks replicate most of the checks that CRAN runs, so we need them all to be passing or to understand that the failures may (though won't necessarily) result in a rejection from CRAN. - [ ] Check [current CRAN check results](https://cran.rstudio.org/web/checks/check_results_arrow.html) - [ ] Ensure the contents of the README are accurate and up to date. - [ ] Run `urlchecker::url_check()` on the R directory at the release candidate. commit. Ignore any errors with badges as they will be removed in the CRAN release branch. - [ ] [Polish NEWS](https://style.tidyverse.org/news.html#news-release) but do **not** update version numbers (this is done automatically later). - [ ] Run preliminary reverse dependency checks using `archery docker run r-revdepcheck`. ## After release candidate has been cut - [ ] Create a CRAN-release branch from the release candidate commit ## Prepare and check the .tar.gz that will be released to CRAN. - [ ] `git fetch upstream && git checkout release-X.X.X-rcXX && git clean -f -d` - [ ] Run `make build`. This copies Arrow C++ into tools/cpp, prunes some unnecessary components, and runs `R CMD build` to generate the source tarball. Because this will install the package, you will need to ensure that the version of Arrow C++ available to the configure script is the same as the version that is vendored into the R package (e.g., you may need to unset `ARROW_HOME`). - [ ] `devtools::check_built("arrow_X.X.X.tar.gz")` locally - [ ] Run reverse dependency checks using `archery docker run r-revdepcheck`. ## Generate R package to submit to CRAN - [ ] Pick any commits that were made to main since the release commit that were needed to fix CRAN-related submission issues identified in the above steps. - [ ] Remove badges from README.md - [ ] Run `urlchecker::url_check()` on the R directory - [ ] Create a PR entitled `WIP: [R] Verify CRAN release-10.0.1-rc0`. Add a comment `@github-actions crossbow submit --group r` to run all R crossbow jobs against the CRAN-specific release branch. - [ ] Regenerate arrow_X.X.X.tar.gz (i.e., `make build`) - [ ] `devtools::check_built("arrow_X.X.X.tar.gz")` locally one more time (for luck) ## CRAN submission - [ ] Upload arrow_X.X.X.tar.gz to the [CRAN submit page](https://xmpalantir.wu.ac.at/cransubmit/) - [ ] Confirm the submission email Wait for CRAN... - [ ] Accepted! - [ ] Tag the tip of the CRAN-specific release branch - [ ] Add a new line to the matrix in the [backwards compatability job](https://github.com/apache/arrow/blob/main/dev/tasks/r/github.linux.arrow.version.back.compat.yml) - [ ] (patch releases only) Update the package version in `ci/scripts/PKGBUILD`, `dev/tasks/homebrew-formulae/autobrew/apache-arrow.rb`, `r/DESCRIPTION`, and `r/NEWS.md` - [ ] (CRAN-only releases) Rebuild the docs with `pkgdown::build_site(examples = FALSE, lazy = TRUE, install = FALSE)` and submit a PR to [the `asf-site` branch of the docs site](https://github.com/apache/arrow-site) with the contents of `r/docs/news/index.html`. - [ ] (CRAN-only releases) Bump the version number in `r/pkgdown/assets/versions.json`, and update this on the [the `asf-site` branch of the docs site](https://github.com/apache/arrow-site) too. - [ ] Update the packaging checklist template to reflect any new realities of the packaging process. - [ ] Wait for CRAN-hosted binaries on the [CRAN package page](https://cran.r-project.org/package=arrow) to reflect the new version ### Component(s) R -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
