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

Hudson commented on HBASE-21988:
--------------------------------

Results for branch branch-2.0
        [build #1400 on 
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/1400/]: 
(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.0/1400//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.0/1400//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/branch-2.0/1400//JDK8_Nightly_Build_Report_(Hadoop3)/]


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


> Remove hadoop2.6.1-hadoop-2.6.4 as supported on branch-2.0
> ----------------------------------------------------------
>
>                 Key: HBASE-21988
>                 URL: https://issues.apache.org/jira/browse/HBASE-21988
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: stack
>            Assignee: stack
>            Priority: Major
>         Attachments: HBASE-21988.branch-2.0.001.patch
>
>
> See tail of parent issue where the parent patch breaks our compat for 
> versions of hadoop before 2.6.4. Rather than remove the parent patch, will 
> retract notion that branch-2.0 works on hadoop-2.6.1-4... Just leave 2.6.5 as 
> supported.
> I'd remove support for hadoop-2.6 completely to align w/ what tip of branch-1 
> says and what rest of branch-2 releases say but branch-2.0 has advertised 
> itself up to this point as supporting hadoop-2.6 so requiring lastest release 
> on that branch seems fine at this point, the EOL of branch-2.0



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to