paleolimbot commented on code in PR #14678: URL: https://github.com/apache/arrow/pull/14678#discussion_r1036060834
########## r/PACKAGING.md: ########## @@ -0,0 +1,129 @@ + +<!--- + Licensed to the Apache Software Foundation (ASF) under one + or more contributor license agreements. See the NOTICE file + distributed with this work for additional information + regarding copyright ownership. The ASF licenses this file + to you under the Apache License, Version 2.0 (the + "License"); you may not use this file except in compliance + with the License. You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, + software distributed under the License is distributed on an + "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY + KIND, either express or implied. See the License for the + specific language governing permissions and limitations + under the License. +--> + +# Packaging checklist for CRAN release + +For a high-level overview of the release process see the +[Apache Arrow Release Management Guide](https://arrow.apache.org/docs/developers/release.html#post-release-tasks). + +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](https://lists.apache.org/list.html?bui...@arrow.apache.org). 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 is accurate +- [ ] 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). +- [ ] For major releases, prepare tweet thread highlighting new features + +Wait for the release candidate to be cut: + +- [ ] Release candidate! + +Make pull requests into the [autobrew](https://github.com/autobrew) and +[rtools-packages](https://github.com/r-windows/rtools-packages) repositories +used by the configure script on MacOS and Windows. These pull requests will +use the release candidate as the source. + +- [ ] Pull request to modify + [the apache-arrow autobrew formula]( https://github.com/autobrew/homebrew-core/blob/high-sierra/Formula/apache-arrow.rb) + to update the release version, SHA256 checksum of the release source file, and any changes to dependencies and build steps that have changed in the + [copy of the formula we have of that formula in the Arrow repo](https://github.com/apache/arrow/blob/master/dev/tasks/homebrew-formulae/autobrew/apache-arrow.rb) +- [ ] Pull request to modify + [the apache-arrow-static autobrew formula]( https://github.com/autobrew/homebrew-core/blob/master/Formula/apache-arrow-static.rb) + to update the version, SHA, and any changes to dependencies and build steps that have changed in the + [copy of the formula we have of that formula in the Arrow repo](https://github.com/apache/arrow/blob/master/dev/tasks/homebrew-formulae/autobrew/apache-arrow-static.rb) +- [ ] Pull request to modify the + [autobrew script](https://github.com/autobrew/scripts/blob/master/apache-arrow) + to include any additions made to + [r/tools/autobrew](https://github.com/apache/arrow/blob/master/r/tools/autobrew). +- [ ] Pull request to modify the + [PKGBUILD script](https://github.com/r-windows/rtools-packages/blob/master/mingw-w64-arrow/PKGBUILD) + to reflect changes in + [ci/PKGBUILD](https://github.com/apache/arrow/blob/master/ci/scripts/PKGBUILD), + uncommenting the line that says "uncomment to test the rc". + +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` +- [ ] `make build` (copies Arrow C++ into tools/cpp, prunes some unnecessary + components, and runs `R CMD build`) +- [ ] `devtools::check("arrow_X.X.X.tar.gz")` locally Review Comment: Oh maybe not. You can do `R CMD check /home/nic2/arrow/r/arrow_10.0.1.tar.gz` for sure though. -- 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: github-unsubscr...@arrow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
