[
https://issues.apache.org/jira/browse/HBASE-21998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16785984#comment-16785984
]
Hudson commented on HBASE-21998:
--------------------------------
Results for branch branch-2.1
[build #926 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.1/926/]:
(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/branch-2.1/926//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.1/926//JDK8_Nightly_Build_Report_(Hadoop2)/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.1/926//JDK8_Nightly_Build_Report_(Hadoop3)/]
(x) {color:red}-1 source release artifact{color}
-- See build output for details.
(x) {color:red}-1 client integration test{color}
-- Something went wrong with this stage, [check relevant console
output|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.1/926//console].
> Move branch-2.1 version from 2.1.4 to 2.1.5-SNAPSHOT
> ----------------------------------------------------
>
> Key: HBASE-21998
> URL: https://issues.apache.org/jira/browse/HBASE-21998
> Project: HBase
> Issue Type: Sub-task
> Components: rm
> Reporter: stack
> Assignee: stack
> Priority: Major
> Fix For: 2.1.5
>
>
> Moving on the version. If we have to make a new RC, the new rm scripts know
> how to deal w/ a version gone too far. The new rm scripts expect the version
> to have been moved on (this is what they do when they are running the
> versioning and tagging of the candidate).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
