From 06bdebb40e29dc782c98842446fdbffaa0b50add Mon Sep 17 00:00:00 2001
From: Zoltan Ivanfi <zi@cloudera.com>
Date: Fri, 23 Nov 2018 15:22:45 +0100
Subject: [PATCH] PARQUET-1462: Allow specifying new development version in
 prepare-release.sh

Currently prepare-release.sh only takes the release version as a
parameter, the new development version is asked interactively for each
individual pom.xml file, which makes answering them tedious.
---
 dev/prepare-release.sh | 18 ++++++++++++------
 1 file changed, 12 insertions(+), 6 deletions(-)
 mode change 100644 => 100755 dev/prepare-release.sh

diff --git a/dev/prepare-release.sh b/dev/prepare-release.sh
old mode 100644
new mode 100755
index 1ced001f8d..04a79a1595
--- a/dev/prepare-release.sh
+++ b/dev/prepare-release.sh
@@ -18,16 +18,22 @@
 # under the License.
 #
 
-if [ -z "$1" ]; then
-  echo "Usage: $0 <version>"
-  exit
+set -e
+
+if [ -z "$2" ]; then
+    cat <<EOF
+Usage: $0 <release-version> <new-development-version-without-SNAPSHOT-suffix>
+Example: $0 1.6.0 1.7.0
+EOF
+  exit 1
 fi
 
-version=$1
+release_version="$1"
+new_development_version="$2-SNAPSHOT"
 
-tag=apache-parquet-$version
+tag="apache-parquet-$release_version"
 
 mvn release:clean
-mvn release:prepare -Dtag=$tag -DreleaseVersion=$version
+mvn release:prepare -Dtag="$tag" "-DreleaseVersion=$release_version" -DdevelopmentVersion="$new_development_version"
 
 echo "Finish staging binary artifacts by running: mvn release:perform"