kudu-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jdcry...@apache.org
Subject kudu git commit: [docs] fixup releasing git instructions
Date Mon, 18 Sep 2017 22:22:15 GMT
Repository: kudu
Updated Branches:
  refs/heads/master 57de48d20 -> a9a1b80ae

[docs] fixup releasing git instructions

Change-Id: I83f98350ddcaf062477db1ee0b90f1811f87524b
Reviewed-on: http://gerrit.cloudera.org:8080/7876
Tested-by: Kudu Jenkins
Reviewed-by: Jean-Daniel Cryans <jdcryans@apache.org>

Project: http://git-wip-us.apache.org/repos/asf/kudu/repo
Commit: http://git-wip-us.apache.org/repos/asf/kudu/commit/a9a1b80a
Tree: http://git-wip-us.apache.org/repos/asf/kudu/tree/a9a1b80a
Diff: http://git-wip-us.apache.org/repos/asf/kudu/diff/a9a1b80a

Branch: refs/heads/master
Commit: a9a1b80ae67b7e75b76a4b8862c77357d450d43b
Parents: 57de48d
Author: Dan Burkert <danburkert@apache.org>
Authored: Tue Aug 29 11:45:42 2017 -0700
Committer: Jean-Daniel Cryans <jdcryans@apache.org>
Committed: Mon Sep 18 22:19:24 2017 +0000

 RELEASING.adoc | 35 ++++++++++++++++++++++++++++++-----
 1 file changed, 30 insertions(+), 5 deletions(-)

diff --git a/RELEASING.adoc b/RELEASING.adoc
index 161e4ac..ebc0039 100644
--- a/RELEASING.adoc
+++ b/RELEASING.adoc
@@ -54,8 +54,8 @@ http://git-wip-us.apache.org/repos/asf?p=kudu.git. The following example
 assumes they are called `cloudera` and `apache`.
-  git push branch-0.9.x cloudera
-  git push branch-0.9.x apache
+  git push cloudera branch-0.9.x
+  git push apache branch-0.9.x
 . Create a new branch on Gerrit. Go to
@@ -77,6 +77,8 @@ branch with the same name and the previously-noted SHA1.
   mvn versions:set -DnewVersion=0.X.0-SNAPSHOT
+. Update the version in `java/gradle.properties`.
 . If the python API has changed since the previous release, bump the Python version
   in `python/setup.py` in master. (the Python API uses separate versioning).
@@ -96,7 +98,8 @@ branch with the same name and the previously-noted SHA1.
 . Fix any issues it finds, such as RAT.
-. Remove the -SNAPSHOT from the version string in `version.txt`.
+. Create a new version update commit which removes the -SNAPSHOT suffix (same
+  process as above).
 . When ready, create a new lightweight tag and push it to the Apache Git repository.
@@ -109,13 +112,31 @@ branch with the same name and the previously-noted SHA1.
 . Create a new folder in https://dist.apache.org/repos/dist/dev/kudu/.
   Copy the artifacts to this folder and commit (it is Subversion).
   svn co --depth=immediates https://dist.apache.org/repos/dist/dev/kudu/
   svn commit -m "Adding Kudu 1.x.0 RC1"
-Initiating a Vote for an RC
+. Create a Maven staging repository for the RC.
+  # Run a gpg-agent if you don't normally
+  gpg-agent --daemon
+  cd java
+  mvn -DskipTests clean -Papache-release clean deploy
+Go to the link:https://repository.apache.org/#stagingRepositories[staging repository]
+and look for ‘orgapachekudu-####’ in the staging repositories list. You can
+check the ‘content’ tab at the bottom to make sure you have all of the expected
+stuff (client, various integrations, both versions of Spark) Hit the checkbox
+next to your new staging repo and hit “close”. Enter “Apache Kudu 1.1.0-RC1” or
+whatever into that box. Wait a minute or two and hit refresh, and your staging
+repo should now have a URL shown in its summary tab (eg
+== Initiating a Vote for an RC
 . Send an email to dev@kudu.apache.org to start the RC process, using
@@ -153,6 +174,10 @@ Apache Git repository:
   git push apache 0.9.2-RC1
+. Release the staged Java artifacts. Select the release candidate staging
+  repository in link:https://repository.apache.org/#stagingRepositories[Nexus],
+  and click 'Release'.
 . Generate the version-specific documentation from that branch following these

View raw message