[
https://issues.apache.org/jira/browse/HBASE-23118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16944594#comment-16944594
]
Hudson commented on HBASE-23118:
--------------------------------
Results for branch master
[build #1493 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/1493/]: (x)
*{color:red}-1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1493//General_Nightly_Build_Report/]
(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1493//JDK8_Nightly_Build_Report_(Hadoop2)/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1493//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> [RELEASE SCRIPTS] Allow creating a RC from an existing tag
> ----------------------------------------------------------
>
> Key: HBASE-23118
> URL: https://issues.apache.org/jira/browse/HBASE-23118
> Project: HBase
> Issue Type: Improvement
> Components: scripts
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Major
> Fix For: 3.0.0
>
>
> Generating the CHANGES.md requires some manual works such as checking whether
> the things in git are the same with on jira, so I'd like to do this manually
> and also make the tag manually.
> So I think the release scripts should have the ability to start making a
> release from an existing tag, instead of always start from the very beginning
> where we will generate and commit CHANGES.md.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
