Releasing Parquet
Setup
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:
- Verify that the release is finished (no planned JIRAs are pending and all patches are cherry-picked to the release branch)
- Resolve all associated JIRAs with correct target version and create the next unreleased version in the JIRA project
- Build and test the project
- Create a new branch for the release if this is a new minor version. For example, if the new minor version is 1.13.0, create a new branch
parquet-1.13.x
- 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 CHANGES.md and update formatting
- Commit the update to CHANGES.md and make sure it is committed to both release and master branches
1. Run the prepare script
dev/prepare-release.sh <version> <rc-number>
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.
- Go to Nexus.
- In the menu on the left, choose “Staging Repositories”.
- Select the Parquet repository.
- At the top, click “Close” and follow the instructions. For the comment use “Apache Parquet [Format] ”.
4. Run the source tarball script
dev/source-release.sh <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 https://dist.apache.org/repos/dist/dev/parquet/
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 dev@parquet.apache.org
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>-rc<NUM>
* https://github.com/apache/parquet-mr/tree/<SHA1>
The release tarball, signature, and checksums are here:
* https://dist.apache.org/repos/dist/dev/parquet/<PATH>
You can find the KEYS file here:
* https://downloads.apache.org/parquet/KEYS
Binary artifacts are staged in Nexus here:
* https://repository.apache.org/content/groups/staging/org/apache/parquet/
This release includes important changes that I should have summarized here, but I'm lazy.
Please download, verify, and test.
Please vote in the next 72 hours.
[ ] +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. Tag final release and set development version
dev/finalize-release <release-version> <rc-num> <new-development-version-without-SNAPSHOT-suffix>
This will add the final release tag to the RC tag and sets the new development version in the pom files. If everything is fine push the changes and the new tag to github: git push --follow-tags
2. Release the binary repository in Nexus
Releasing a binary repository publishes the binaries to public.
- Go to Nexus.
- In the menu on the left, choose “Staging Repositories”.
- Select the Parquet repository.
- At the top, click Release and follow the instructions. For the comment use “Apache Parquet [Format] ”.
3. Copy the release artifacts in SVN into releases
First, check out the candidates and releases locations in SVN:
mkdir parquet
cd parquet
svn co https://dist.apache.org/repos/dist/dev/parquet candidates
svn co https://dist.apache.org/repos/dist/release/parquet 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>"
4. Update parquet.apache.org
Update the downloads page on parquet.apache.org. Instructions for updating the site are on the contribution page.
5. Send an ANNOUNCE e-mail to announce@apache.org 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: https://github.com/apache/parquet-mr/blob/apache-parquet-<VERSION>/CHANGES.md
This release can be downloaded from: https://parquet.apache.org/downloads/
Java artifacts are available from Maven Central.
Thanks to everyone for contributing!