chore: Go through verification instructions + update where needed (#305)
diff --git a/dev/release/README.md b/dev/release/README.md
index 474e3fe..4ecc67e 100644
--- a/dev/release/README.md
+++ b/dev/release/README.md
@@ -25,12 +25,12 @@
prior to a release vote being called on the
[Apache Arrow developer mailing list](https://lists.apache.org/list.html?dev@arrow.apache.org).
A script (`verify-release-candidate.sh`) is provided to verify such a release candidate.
-For example, to verify nanoarrow 0.2.0-rc0, one could run:
+For example, to verify nanoarrow 0.3.0-rc0, one could run:
```bash
git clone https://github.com/apache/arrow-nanoarrow.git arrow-nanoarrow
cd arrow-nanoarrow/dev/release
-./verify-release-candidate.sh 0.2.0 0
+./verify-release-candidate.sh 0.3.0 0
```
Full verification requires [CMake](https://cmake.org/download/) to build and run the test
@@ -56,13 +56,13 @@
To run only C library verification (requires CMake and Arrow C++ but not R):
```bash
-TEST_DEFAULT=0 TEST_C=1 TEST_C_BUNDLED=1 ./verify-release-candidate.sh 0.2.0 0
+TEST_DEFAULT=0 TEST_C=1 TEST_C_BUNDLED=1 ./verify-release-candidate.sh 0.3.0 0
```
To run only R package verification (requires R but not CMake or Arrow C++):
```bash
-TEST_DEFAULT=0 TEST_R=1 ./verify-release-candidate.sh 0.2.0 0
+TEST_DEFAULT=0 TEST_R=1 ./verify-release-candidate.sh 0.3.0 0
```
### MacOS
@@ -114,7 +114,7 @@
conda install -c conda-forge compilers git cmake arrow-cpp
# For R (see below about potential interactions with system R
# before installing via conda on MacOS)
-conda install -c conda-forge r-testthat r-hms r-blob r-pkgbuild
+conda install -c conda-forge r-testthat r-hms r-blob r-pkgbuild r-bit64
```
Note that using conda-provided R when there is also a system install of R
@@ -148,7 +148,7 @@
cd ..
# Pass location of Arrow and R to the verification script
-export NANOARROW_CMAKE_OPTIONS="-DArrow_DIR=$(pwd -W)/arrow/lib/cmake/Arrow gtest_force_shared_crt=ON"
+export NANOARROW_CMAKE_OPTIONS="-DArrow_DIR=$(pwd -W)/arrow/lib/cmake/Arrow -Dgtest_force_shared_crt=ON -DNANOARROW_ARROW_STATIC=ON"
export R_HOME="/c/Program Files/R/R-4.2.2"
```
@@ -257,7 +257,7 @@
## Creating a release candidate
The first step to creating a nanoarrow release is to create a `maint-VERSION` branch
-(e.g., `usethis::pr_init("maint-0.2.0")`) and push the branch to `upstream`. This is
+(e.g., `usethis::pr_init("maint-0.3.0")`) and push the branch to `upstream`. This is
a good opportunity to run though the above instructions to make sure the verification
script and instructions are up-to-date. You may also wish to start a manual dispatch
of the [Verification workflow](https://github.com/apache/arrow-nanoarrow/actions/workflows/verify.yaml)
@@ -268,11 +268,11 @@
```bash
# from the repository root
# 01-prepare.sh <nanoarrow-dir> <prev_veresion> <version> <next_version> <rc-num>
-dev/release/01-prepare.sh . 0.0.0 0.2.0 0.3.0 0
+dev/release/01-prepare.sh . 0.0.0 0.3.0 0.4.0 0
```
This will update version numbers, the changelong, and create the git tag
-`apache-arrow-nanoarrow-0.2.0-rc0`. Check to make sure that the changelog
+`apache-arrow-nanoarrow-0.3.0-rc0`. Check to make sure that the changelog
and versions are what you expect them to be before pushing the tag (you
may wish to do this by opening a dummy PR to run CI and look at the diff
from the main branch). When you are satisfied that the code at this tag
@@ -294,7 +294,7 @@
```bash
# 02-sign.sh <version> <rc-num>
-dev/release/02-sign.sh 0.2.0 0
+dev/release/02-sign.sh 0.3.0 0
```
Finally, run
@@ -306,7 +306,7 @@
```
# 03-source.sh $0 <version> <rc-num>
-dev/release/03-source.sh 0.2.0 0
+dev/release/03-source.sh 0.3.0 0
```
You should check that the release verification runs locally and/or
@@ -318,26 +318,26 @@
```
Hello,
-I would like to propose the following release candidate (RC{rc_num}) of Apache Arrow nanoarrow [0] version {version}. This is an initial release consisting of {num_resolved_issues} resolved GitHub issues [1].
+I would like to propose the following release candidate (rc0) of Apache Arrow nanoarrow [0] version 0.3.0. This is an initial release consisting of 42 resolved GitHub issues from 4 contributors [1].
This release candidate is based on commit: {rc_commit} [2]
-The source release rc{rc_num} is hosted at [3].
+The source release rc0 is hosted at [3].
The changelog is located at [4].
Please download, verify checksums and signatures, run the unit tests, and vote on the release. See [5] for how to validate a release candidate.
The vote will be open for at least 72 hours.
-[ ] +1 Release this as Apache Arrow nanoarrow {version}
+[ ] +1 Release this as Apache Arrow nanoarrow 0.3.0
[ ] +0
-[ ] -1 Do not release this as Apache Arrow nanoarrow {version} because...
+[ ] -1 Do not release this as Apache Arrow nanoarrow 0.3.0 because...
[0] https://github.com/apache/arrow-nanoarrow
-[1] https://github.com/apache/arrow-nanoarrow/milestone/{milestone}?closed=1
-[2] https://github.com/apache/arrow-nanoarrow/tree/apache-arrow-nanoarrow-{version}-rc{rc_num}
-[3] https://dist.apache.org/repos/dist/dev/arrow/apache-arrow-nanoarrow-{version}-rc{rc_num}/
-[4] https://github.com/apache/arrow-nanoarrow/blob/apache-arrow-nanoarrow-{version}-rc{rc_num}/CHANGELOG.md
+[1] https://github.com/apache/arrow-nanoarrow/milestone/3?closed=1
+[2] https://github.com/apache/arrow-nanoarrow/tree/apache-arrow-nanoarrow-0.3.0-rc0
+[3] https://dist.apache.org/repos/dist/dev/arrow/apache-arrow-nanoarrow-0.3.0-rc0/
+[4] https://github.com/apache/arrow-nanoarrow/blob/apache-arrow-nanoarrow-0.3.0-rc0/CHANGELOG.md
[5] https://github.com/apache/arrow-nanoarrow/blob/main/dev/release/README.md
```
@@ -367,7 +367,7 @@
The reporter system for Arrow can be found at
<https://reporter.apache.org/addrelease.html?arrow>. To add a release, a
PMC member must log in with their Apache username/password. The release
-names are in the form `NANOARROW-0.2.0`.
+names are in the form `NANOARROW-0.3.0`.
### Upload artifacts to Subversion / Create GitHub Release
@@ -377,7 +377,7 @@
has been set in `.env`.
```bash
-dev/release/post-01-upload.sh 0.2.0 0
+dev/release/post-01-upload.sh 0.3.0 0
```
### Submit R package to CRAN
@@ -389,8 +389,8 @@
`usethis::use_release_issue()` should all be completed (i.e., any changes
after release should be minor tweaks). The steps are:
-- Ensure you are on the release branch (i.e., `git switch maint-0.2.0`)
-- Run `usethis::pr_init("r-cran-maint-0.2.0")` and push the branch to your
+- Ensure you are on the release branch (i.e., `git switch maint-0.3.0`)
+- Run `usethis::pr_init("r-cran-maint-0.3.0")` and push the branch to your
fork.
- Ensure `cran_comments.md` is up-to-date.
- Run `devtools::check()` locally and verify that the package version is correct
@@ -402,7 +402,7 @@
Any changes required at this stage should be made as a PR into `main` and
cherry-picked into the `r-cran-maint-XXX` packaging branch. (i.e.,
`git cherry-pick 01234abcdef`). If any changes
-to the source are required, bump the "tweak" version (e.g., `Version: 0.2.0.1`
+to the source are required, bump the "tweak" version (e.g., `Version: 0.3.0.1`
in `DESCRIPTION`).
### Release blog post
@@ -419,14 +419,14 @@
Email template:
```
-[ANNOUNCE] Apache Arrow nanoarrow 0.2.0 Released
+[ANNOUNCE] Apache Arrow nanoarrow 0.3.0 Released
-The Apache Arrow community is pleased to announce the 0.2.0 release of Apache Arrow nanoarrow. This initial release covers 31 resolved issues from 6 contributors[1].
+The Apache Arrow community is pleased to announce the 0.3.0 release of Apache Arrow nanoarrow. This initial release covers 42 resolved issues from 4 contributors[1].
The release is available now from [2].
Release notes are available at:
-https://github.com/apache/arrow-nanoarrow/blob/apache-arrow-nanoarrow-0.2.0/CHANGELOG.md
+https://github.com/apache/arrow-nanoarrow/blob/apache-arrow-nanoarrow-0.3.0/CHANGELOG.md
What is Apache Arrow?
---------------------
@@ -442,8 +442,8 @@
Regards,
The Apache Arrow Community
-[1]: https://github.com/apache/arrow-nanoarrow/issues?q=is%3Aissue+milestone%3A%22nanoarrow+0.2.0%22+is%3Aclosed
-[2]: https://www.apache.org/dyn/closer.cgi/arrow/apache-arrow-nanoarrow-0.2.0
+[1]: https://github.com/apache/arrow-nanoarrow/issues?q=is%3Aissue+milestone%3A%22nanoarrow+0.3.0%22+is%3Aclosed
+[2]: https://www.apache.org/dyn/closer.cgi/arrow/apache-arrow-nanoarrow-0.3.0
[3]: https://github.com/apache/arrow-nanoarrow
[4]: https://lists.apache.org/list.html?user@arrow.apache.org
[5]: https://lists.apache.org/list.html?dev@arrow.apache.org
@@ -459,7 +459,7 @@
# Once
export APACHE_USERNAME=xxx
# Once for every release candidate
-svn rm --username=$APACHE_USERNAME -m "Clean up svn artifacts" https://dist.apache.org/repos/dist/dev/arrow/apache-arrow-nanoarrow-0.2.0-rc0/
+svn rm --username=$APACHE_USERNAME -m "Clean up svn artifacts" https://dist.apache.org/repos/dist/dev/arrow/apache-arrow-nanoarrow-0.3.0-rc0/
```
### Bumped versions on main
@@ -468,5 +468,5 @@
[post-02-bump-versions.sh](https://github.com/apache/arrow-nanoarrow/blob/main/dev/release/post-02-bump-versions.sh):
```bash
-dev/release/post-02-bump-versions.sh . 0.2.0 0.3.0
+dev/release/post-02-bump-versions.sh . 0.3.0 0.4.0
```
