You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@hbase.apache.org by st...@apache.org on 2019/03/30 20:09:41 UTC
[hbase-thirdparty] branch master updated: Some doc on how to do an
RC
This is an automated email from the ASF dual-hosted git repository.
stack pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/hbase-thirdparty.git
The following commit(s) were added to refs/heads/master by this push:
new 09951aa Some doc on how to do an RC
09951aa is described below
commit 09951aa6847d745d61ee92bbe9304beb8a62430b
Author: stack <st...@apache.org>
AuthorDate: Sat Mar 30 13:09:24 2019 -0700
Some doc on how to do an RC
---
README.txt | 66 ++++++++++++++++++++++++++++++++++++++++++++---
src/main/assembly/src.xml | 3 ++-
2 files changed, 64 insertions(+), 5 deletions(-)
diff --git a/README.txt b/README.txt
index 2576d04..27dbea5 100644
--- a/README.txt
+++ b/README.txt
@@ -37,12 +37,70 @@ To deploy to mvn central, run:
$ mvn install deploy -Papache-release -Prelease
+(Make sure you have your credentials set over in ~/.m2/settings.xml, etc. -- see
+hbase refguide for publishing SNAPSHOTS/Release Candidates)
+
To build a src tarball:
$ mvn clean assembly:single
-(Make sure you have your credentials set over in ~/.m2/settings.xml, etc. -- see
-hbase refguide for publishing SNAPSHOTS/Release Candidates)
+To cut a release candidate, update JIRA. The hbase-thirdparty
+currently uses hbase JIRA but with versions specified with a
+''thirdparty-' prefix as in thirdparty-2.2.0.
+
+To generate the source tarball do as follows (below uses 2.2.0
+as target version and 2.2.0RC0 as the tag to use):
+
+ $ git archive --format=tar.gz --output=../hbase-thirdparty-2.2.0-src.tar.gz --prefix="hbase-thirdparty-2.2.0/" 2.2.0RC0
+
+Sign and get the hash of the tgz:
+
+ $ gpg --print-md SHA512 hbase-thirdparty-2.2.0-src.tar.gz > hbase-thirdparty-2.2.0-src.tar.gz.sha512
+ $ gpg --armour --output hbase-thirdparty-2.2.0-src.tar.gz.asc --detach-sig hbase-thirdparty-2.2.0-src.tar.gz
+
+Check in the content under apache/dist in hbase/thirdparty:
+
+ $ cp -r dir_of_artifacts ~/checkouts/apache.dist/dev/hbase/hbase-thirdparty/hbase-thirdparty-2.2.0RC0
+
+Add the dir and commit it.
+
+Now upload to the maven staging repository:
+
+ $ mvn install deploy -Papache-release -Prelease
+
+Login to repository.apache.org and 'close' the uploaded repo.
+
+Try the new artifact by having hbase use the staged jar. Do this in your hbase pom:
+
+diff --git a/pom.xml b/pom.xml
+index 112f95a892..dab9e7a6bd 100755
+--- a/pom.xml
++++ b/pom.xml
+@@ -1451,7 +1451,7 @@
+ <spotbugs.version>3.1.0-RC3</spotbugs.version>
+ <wagon.ssh.version>2.12</wagon.ssh.version>
+ <xml.maven.version>1.0.1</xml.maven.version>
+- <hbase-thirdparty.version>2.1.0</hbase-thirdparty.version>
++ <hbase-thirdparty.version>2.2.0</hbase-thirdparty.version>
+ <!-- Intraproject jar naming properties -->
+ <!-- TODO this is pretty ugly, but works for the moment.
+ Modules are pretty heavy-weight things, so doing this work isn't too bad. -->
+@@ -3774,4 +3774,11 @@
+ <url>file:///tmp</url>
+ </site>
+ </distributionManagement>
++ <repositories>
++ <repository>
++ <id>staging</id>
++ <name>staging</name>
++ <url>https://repository.apache.org/content/repositories/orgapachehbase-1296</url>
++ </repository>
++ </repositories>
+ </project>
+
+Send out an email with details on staging repo and pointers to the uploaded
+artifacts.
+
+
+
-There is no CHANGES.md just yet as this project does not have its own
-dedicated JIRA or JIRA label for filing issues against. TODO.
diff --git a/src/main/assembly/src.xml b/src/main/assembly/src.xml
index 4b8ca31..9ef6c9c 100644
--- a/src/main/assembly/src.xml
+++ b/src/main/assembly/src.xml
@@ -69,7 +69,8 @@
<include>pom.xml</include>
<include>LICENSE.txt</include>
<include>NOTICE.txt</include>
- <include>CHANGES.txt</include>
+ <include>CHANGES.md</include>
+ <include>RELEASENOTES.md</include>
<include>README.txt</include>
</includes>
<fileMode>0644</fileMode>