[ 
https://issues.apache.org/jira/browse/HBASE-25580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17294536#comment-17294536
 ] 

Hudson commented on HBASE-25580:
--------------------------------

Results for branch master
        [build #225 on 
builds.a.o|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/master/225/]:
 (x) *{color:red}-1 overall{color}*
----
details (if available):

(/) {color:green}+1 general checks{color}
-- For more information [see general 
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/master/225/General_20Nightly_20Build_20Report/]






(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) 
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/master/225/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11 
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/master/225/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 source release artifact{color}
-- See build output for details.


(/) {color:green}+1 client integration test{color}


> Release scripts should include in the vote email the git hash that the RC tag 
> points to
> ---------------------------------------------------------------------------------------
>
>                 Key: HBASE-25580
>                 URL: https://issues.apache.org/jira/browse/HBASE-25580
>             Project: HBase
>          Issue Type: Task
>          Components: community
>            Reporter: Sean Busbey
>            Assignee: Sean Busbey
>            Priority: Major
>             Fix For: 3.0.0-alpha-1
>
>
> the git tags for release candidates are not protected, so they could change 
> after a RM posts a release candidate. the vote text should include the git 
> hash that the RC tag points to at the time of the vote so a change can easily 
> be seen.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to