Release Verification Process#

This page provides detailed information on the steps followed to performa release verification on the major platforms.

Principles#

The Apache Arrow Release Approval process follows the guidelines defined at theApache Software Foundation Release Approval.

For a release vote to pass, a minimum of three positive binding votes and morepositive binding votes than negative binding votes MUST be cast.Releases may not be vetoed. Votes cast by PMC members are binding, however,non-binding votes are greatly encouraged and a sign of a healthy project.

Running the release verification#

Linux and macOS#

In order to run the verification script either for the source release or thebinary artifacts see the following guidelines:

Required source verification#

Individuals are REQUIRED to download all signed source code packages onto theirown hardware, validate all cryptographic signatures, compile as provided,and test the result on their own platform in order to cast a +1 vote.

# this will create and automatically clean up a temporary directory for the verification environment and will run the source verificationTEST_DEFAULT=0 TEST_SOURCE=1 verify-release-candidate.sh $VERSION $RC_NUM# to verify only certain implementations use the TEST_DEFAULT=0 and TEST_* variables# here are a couple of examples, but see the source code for the available optionsTEST_DEFAULT=0 TEST_CPP=1 verify-release-candidate.sh $VERSION $RC_NUM  # only C++ testsTEST_DEFAULT=0 TEST_CPP=1 TEST_PYTHON=1 verify-release-candidate.sh $VERSION $RC_NUM  # C++ and Python testsTEST_DEFAULT=0 TEST_INTEGRATION_CPP=1 TEST_INTEGRATION_JAVA=1 verify-release-candidate.sh $VERSION $RC_NUM  # C++ and Java integration tests

Binary verification#

The binaries are generated from the source that has been verified. Those binaries aretested on CI but can be tested locally for further validation. It is not necessary totest them in order to cast a positive vote.

# this will create and automatically clean up a temporary directory for the verification environment and will run the binary verificationTEST_DEFAULT=0 TEST_BINARIES=1 dev/release/verify-release-candidate.sh $VERSION $RC_NUM# to verify certain binaries use the TEST_* variables as:TEST_DEFAULT=0 TEST_WHEELS=1 verify-release-candidate.sh $VERSION $RC_NUM  # only WheelsTEST_DEFAULT=0 TEST_APT=1 verify-release-candidate.sh $VERSION $RC_NUM  # only APT packagesTEST_DEFAULT=0 TEST_YUM=1 verify-release-candidate.sh $VERSION $RC_NUM  # only YUM packagesTEST_DEFAULT=0 TEST_JARS=1 verify-release-candidate.sh $VERSION $RC_NUM  # only JARS

Windows#

In order to run the verification script on Windows you have to downloadthe source tarball from the SVN dist system that you wish to verify:

dev\release\verify-release-candidate.bat%VERSION%%RC_NUM%

System Configuration Instructions#

You will need some tools installed like curl, git, etcetera.

Ubuntu#

You might have to install some packages on your system. The followingutility script can be used to set your Ubuntu system. This wil installthe required packages to perform a source verification on a cleanUbuntu:

# From the arrow clonesudodev/release/setup-ubuntu.sh

macOS ARM#

# From the arrow clonebrewinstallgpgbrewbundle--file=cpp/Brewfilebrewbundle--file=c_glib/Brewfilebrewuninstallnode# You might need to add node, ruby java and maven to the PATH, follow# instructions from brew after installing.brewinstallnode@20brewinstallrubybrewinstallopenjdkbrewinstallmaven

Windows 11#

To be defined

Casting your vote#

Once you have performed the verification you can cast your vote by respondingto the vote thread ondev@arrow.apache.org and supply your result.

If the verification was successful you can send your +1 vote. We usually sendalong with the vote the command that was executed and the local versions used.As an example:

+1I've verified successfully the sources and binaries with:TEST_DEFAULT=0TEST_SOURCE=1dev/release/verify-release-candidate.sh15.0.01with:*Python3.10.12*gcc(Ubuntu11.4.0-1ubuntu1~22.04)11.4.0*NVIDIACUDABuildcuda_11.5.r11.5/compiler.30672275_0*openjdkversion"17.0.9"2023-10-17*ruby3.0.2p107(2021-07-07revision0db68f0233)[x86_64-linux-gnu]*dotnet8.0.204*Ubuntu22.04LTS

If there were some issues during verification please report them on themail thread to diagnose the issue.