Some steps of the release require being a committer or a PMC member.

• Install theArchery utility which is required for the release.

• You must not have any arrow-cpp or parquet-cpp environment variables defined except CC or CXX if you want to build with something other than GCC by default (e.g. clang).

• A GPG key in the Apache Web of Trust to sign binary artifacts. This will have to be cross signed by other Apache committers/PMC members. If you have multiple GPG keys, you must set the correct GPG key ID in~/.gnupg/gpg.conf by adding:

default-key ${YOUR_GPG_KEY_ID}

• The GPG key needs to be added to thisSVN repo andthis one.

• Have the build requirements for cpp and c_glib installed.

• Installen_US.UTF-8 locale. You can confirm available locales bylocale-a.

• Install Python 3 as python

• Create dev/release/.env from dev/release/.env.example. See the comments in dev/release/.env.example how to set each variable.

• SetupCrossbow as defined.

• Have Docker and Docker Compose installed.

• Have GitHub CLI installed.

Mergerelease-X.Y.Z-rcN tomaint-X.Y.Z:

# git checkout maint-10.0.0gitcheckoutmaint-X.Y.Z# git merge release-10.0.0-rc0gitmergerelease-X.Y.Z-rcN# git push -u upstream maint-10.0.0gitpush-uupstreammaint-X.Y.Z

Add relevant release data for Arrow toApache reporter.

A committer must push the release tag to GitHub:

# dev/release/post-01-tag.sh 0.1.0 0dev/release/post-01-tag.sh<version><rc>

A PMC member must commit the source release artifacts to Subversion:

# dev/release/post-02-upload.sh 0.1.0 0dev/release/post-02-upload.sh<version><rc>

A committer must upload the binary release artifacts to Artifactory and create the GitHub Release:

# dev/release/post-03-binary.sh 0.1.0 0dev/release/post-03-binary.sh<version><rcnumber>

Add a release note for the new version to our website and update the latest release information:

## Prepare your fork of https://github.com/apache/arrow-site .## You need to do this only once.# git clone git@github.com:kou/arrow-site.git ../gitclonegit@github.com:<YOUR_GITHUB_ID>/arrow-site.git../cd../arrow-site## Add git@github.com:apache/arrow-site.git as "upstream" remote.gitremoteaddupstreamgit@github.com:apache/arrow-site.gitcd-## Generate a release note for the new version, update the## latest release information automatically.# dev/release/post-04-website.sh 9.0.0 10.0.0dev/release/post-04-website.shOLD_X.OLD_Y.OLD_ZX.Y.Z

This script pushes arelease-note-X.Y.Z branch to yourapache/arrow-site fork. You need to open a pull request from therelease-note-X.Y.Z branch on your Web browser.

A committer must run the following script. This has to be done once thePull Request from the Update Website script has been merged:

# dev/release/post-05-update-gh-release-notes.sh 17.0.0dev/release/post-05-update-gh-release-notes.sh<version>

Open a pull request to Homebrew:

## You need to run this on macOS or Linux that Homebrew is installed.## Fork https://github.com/Homebrew/homebrew-core on GitHub.## You need to do this only once.#### Prepare your fork of https://github.com/Homebrew/homebrew-core .## You need to do this only once.cd"$(brew--repositoryhomebrew/core)"# git remote add kou git@github.com:kou/homebrew-core.gitgitremoteadd<YOUR_GITHUB_ID>git@github.com:<YOUR_GITHUB_ID>/homebrew-core.gitcd-# dev/release/post-12-homebrew.sh 10.0.0 koudev/release/post-12-homebrew.shX.Y.Z<YOUR_GITHUB_ID>

This script pushes aapache-arrow-X.Y.Z branch to yourHomebrew/homebrew-core fork. You need to create a pull request from theapache-arrow-X.Y.Z branch withapache-arrow,apache-arrow-glib:X.Y.Z title on your Web browser.

Open a pull request to MSYS2:

## Fork https://github.com/msys2/MINGW-packages on GitHub.## You need to do this only once.#### Prepare your fork of https://github.com/msys2/MINGW-packages .## You need to do this only once.# git clone git@github.com:kou/MINGW-packages.git ../gitclonegit@github.com:<YOUR_GITHUB_ID>/MINGW-packages.git../cd../MINGW-packages## Add https://github.com/msys2/MINGW-packages.git as "upstream" remote.gitremoteaddupstreamhttps://github.com/msys2/MINGW-packages.gitcd-# dev/release/post-11-msys2.sh 10.0.0 ../MINGW-packagesdev/release/post-11-msys2.shX.Y.Z<YOUR_MINGW_PACKAGES_FORK>

This script pushes aarrow-X.Y.Z branch to yourmsys2/MINGW-packages fork. You need to create a pull request from thearrow-X.Y.Z branch witharrow:UpdatetoX.Y.Z title on your Web browser.

You need an account onhttps://rubygems.org/ to release Ruby packages.

If you have an account onhttps://rubygems.org/ , you need to join owners of our gems.

Existing owners can add a new account to the owners of them by the following command line:

# dev/release/account-ruby.sh raulcddev/release/account-ruby.shNEW_ACCOUNT

Update RubyGems after Homebrew packages and MSYS2 packages are updated:

# dev/release/post-06-ruby.sh 10.0.0dev/release/post-06-ruby.shX.Y.Z

pip binary packages (called “wheels”) and source package (called “sdist”) are built using the crossbow tool that we used above during the release candidate creation process and then uploaded to PyPI (Python Package Index) under the pyarrow package.

We use the twine tool to upload wheels to PyPI:

# dev/release/post-09-python.sh 10.0.0dev/release/post-09-python.sh<version>

To publish the R package on CRAN, there are a few steps we need to do firstin order to ensure that binaries for Windows and macOS are available to CRAN.Jeroen Ooms <jeroenooms@gmail.com> maintains several projects that build C++dependencies for R packages for macOS and Windows. We test copies of thesesame build scripts in our CI, and at release time, we need to send anychanges we have and update the versions/hashes upstream.

When the release candidate is made, make draft pull requests to eachrepository using the rc, updating the version and SHA, as well as any cmakebuild changes from the corresponding files in apache/arrow. Jeroen maymerge these PRs before the release vote passes, build the binary artifacts,and publish them in the right places so that we can do pre-submission checks(see below). After the release candidate vote passes, update these PRsto point to the official (non-rc) URL and mark them as ready for review.Jeroen will merge, build the binary artifacts, and publish them in theright places. See thepackaging checklist.for a precise list of pull requests that must be made prior to submissionto CRAN.

Once these binary prerequisites have been satisfied, we can submit to CRAN.Given the vagaries of the process, it is best if the R developers on theproject verify the CRAN-worthiness of the package before submitting.Our CI systems give us some coverage for the things that CRAN checks, butthere are a couple of final tests we should do to confirm that the releasebinaries will work and that everything runs on the same infrastructure thatCRAN has, which is difficult/impossible to emulate fully with Docker. For aprecise list of checks, see thepackaging checklist.

Once all checks are clean, we submit to CRAN, which has a web form foruploading packages. The release process requires email confirmationfrom the R package maintainer, currently Neal Richardson.

Open a pull request to vcpkg:

## Fork https://github.com/microsoft/vcpkg on GitHub.## You need to do this only once.#### Prepare your fork of https://github.com/microsoft/vcpkg .## You need to do this only once.# git clone git@github.com:kou/vcpkg.git ../gitclonegit@github.com:<YOUR_GITHUB_ID>/vcpkg.git../cd../vcpkg./bootstrap-vcpkg.sh## Add https://github.com/microsoft/vcpkg.git as "upstream" remote.gitremoteaddupstreamhttps://github.com/microsoft/vcpkg.gitcd-# dev/release/post-13-vcpkg.sh 10.0.0 ../vcpkgdev/release/post-13-vcpkg.shX.Y.Z<YOUR_VCPKG_FORK>

This script pushes aarrow-X.Y.Z branch to yourmicrosoft/vcpkg fork. You need to create a pull request from thearrow-X.Y.Z branch with[arrow]UpdatetoX.Y.Z title on your Web browser.

Open a pull request to Conan:

## Fork https://github.com/conan-io/conan-center-index on GitHub.## You need to do this only once.#### Prepare your fork of https://github.com/conan-io/conan-center-index .## You need to do this only once.# git clone git@github.com:kou/conan-center-index.git ../gitclonegit@github.com:<YOUR_GITHUB_ID>/conan-center-index.git../cd../conan-center-index## Add https://github.com/conan-io/conan-center-index.git as "upstream" remote.gitremoteaddupstreamhttps://github.com/conan-io/conan-center-index.gitcd-# dev/release/post-14-conan.sh 10.0.1 ../conan-center-indexdev/release/post-14-conan.shX.Y.Z<YOUR_CONAN_CENTER_INDEX_FORK>

This script pushes aarrow-X.Y.Z branch to yourconan-io/conan-center-index fork. You need to create a pull request from thearrow-X.Y.Z branch on your Web browser.

Documentation is generated as part of the release process. We just need toupload the generated documentation:

## Prepare your fork of https://github.com/apache/arrow-site .## You need to do this only once.# git clone git@github.com:kou/arrow-site.git ../gitclonegit@github.com:<YOUR_GITHUB_ID>/arrow-site.git../cd../arrow-site## Add git@github.com:apache/arrow-site.git as "upstream" remote.gitremoteaddupstreamgit@github.com:apache/arrow-site.gitcd-# dev/release/post-08-docs.sh 10.0.0 9.0.0dev/release/post-08-docs.shX.Y.ZPREVIOUS_X.PREVIOUS_Y.PREVIOUS_Z

This script pushes arelease-docs-X.Y.Z branch to yourarrow-site fork. You need to create a Pull Request and use theasf-site branch as base for it.

Followthe documentationin the Apache Arrow Cookbook repository

Write a release announcement (seeexample) and send toannounce@apache.org anddev@arrow.apache.org.

The announcement toannounce@apache.org must be sent from your apache.org e-mail address to be accepted.

The blog post process isn’t automated. The rough set of steps we usually takeare:

• Cloneapache/arrow-site.

• Create a new branch offmain for the blog post pull request we’recreating.

• Duplicate a recent blog post entry in the_posts subfolder and updatethe filename and YAML metadata.

  • Set the date in the filename and in the YAML metadata to the date that therelease candidate vote thread for the release closed (in GMT).

• For minor releases only, remove any section about community updates (newcommitters, PMC members, etc).

• Update the remainder of the text as needed

• Create the pull request

• In the pull request, ping contributors in each section requesting helpfilling in the details for each section.

Post about the release and link to the blog post on social media. The projecthas two official accounts:

• BlueSky:@arrow.apache.org

• LinkedIn:https://www.linkedin.com/company/apache-arrow/

PMC members have access or can request access to post under these accounts.

Remove RC artifacts onhttps://dist.apache.org/repos/dist/dev/arrow/ and old release artifacts onhttps://dist.apache.org/repos/dist/release/arrow to followthe ASF policy:

dev/release/post-07-remove-old-artifacts.sh

Note: This step must be done by a PMC member.