How to release


You will need: * PGP code signing keys, published in KEYS * Permission to stage artifacts in Nexus

Make sure you have permission to deploy Parquet artifacts to Nexus by pushing a snapshot:

mvn deploy

If you have problems, read the publishing Maven artifacts documentation

Release process

Parquet uses the maven-release-plugin to tag a release and push binary artifacts to staging in Nexus. Once maven completes the release, the offical source tarball is built from the tag.

Before you start the release process:

  1. Verify that the release is finished (no planned JIRAs are pending)
  2. Build and test the project
  3. Update the change log
    • Go to the release notes for the release in JIRA
    • Copy the HTML and convert it to markdown with an online converter
    • Add the content to and update formatting
    • Commit the update to

1. Run the prepare script

sh dev/ <version>

This runs maven’s release prepare with a consistent tag name. After this step, the release tag will exist in the git repository.

If this step fails, you can roll back the changes by running these commands.

find ./ -type f -name '*.releaseBackup' -exec rm {} \;
find ./ -type f -name 'pom.xml' -exec git checkout {} \;

2. Run release:perform to stage binaries

mvn release:perform

This uploads binary artifacts for the release tag to Nexus.

3. In Nexus, close the staging repository

Closing a staging repository makes the binaries available in staging, but does not publish them.

  1. Go to Nexus.
  2. In the menu on the left, choose “Staging Repositories”.
  3. Select the Parquet repository.
  4. At the top, click “Close” and follow the instructions. For the comment use “Apache Parquet [Format] ”.

4. Run the source tarball script

sh dev/ <version> <rc-number>

This script builds the source tarball from the release tag’s SHA1, signs it, and uploads the necessary files with SVN.

The source release is pushed to

The last message from the script is the release commit’s SHA1 hash and URL for the VOTE e-mail.

5. Send a VOTE e-mail to

Here is a template you can use. Make sure everything applies to your release.

Subject: [VOTE] Release Apache Parquet <VERSION> RC<NUM>
Hi everyone,

I propose the following RC to be released as official Apache Parquet <VERSION> release.

The commit id is <SHA1>
* This corresponds to the tag: apache-parquet-<VERSION>

The release tarball, signature, and checksums are here:

You can find the KEYS file here:

Binary artifacts are staged in Nexus here:

This release includes important changes that I should have summarized here, but I'm lazy.

Please download, verify, and test.

Please vote by <72 HOUR FROM NOW>

[ ] +1 Release this as Apache Parquet <VERSION>
[ ] +0
[ ] -1 Do not release this because...

Publishing after the vote passes

After a release candidate passes a vote, the candidate needs to be published as the final release.

1. Release the binary repository in Nexus

2. Copy the release artifacts in SVN into releases

First, check out the candidates and releases locations in SVN:

mkdir parquet
cd parquet
svn co candidates
svn co releases

Next, copy the directory for the release candidate the passed from candidates to releases and rename it; remove the “-rcN” part of the directory name.

cp -r candidates/apache-parquet-<VERSION>-rcN/ releases/apache-parquet-<VERSION>

Then add and commit the release artifacts:

cd releases
svn add apache-parquet-<version>
svn ci -m "Parquet: Add release <VERSION>"

3. Send an ANNOUNCE e-mail to and the dev list

[ANNOUNCE] Apache Parquet release <VERSION>
I'm please to announce the release of Parquet <VERSION>!

Parquet is a general-purpose columnar file format for nested data. It uses
space-efficient encodings and a compressed and splittable structure for
processing frameworks like Hadoop.

Changes are listed at: <CHANGES-URL>

This release can be downloaded from:

Java artifacts are available from Maven Central.

Thanks to everyone for contributing!

4. Update

Instructions for updating the site are on the contribution page.

What to do if a vote fails

If a vote fails, you need to remove the release tag that was created by the dev/ script:

git tag -d apache-parquet-<VERSION> # delete locally
git push apache :apache-parquet-<VERSION> # delete in the Apache repo

Then, use the release process above to build another RC for the release version.