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

Sean Busbey commented on HBASE-19983:
-------------------------------------

whew. surprisingly lots of digging

* [Hadoop PMC labeled 2.8.2 as "stable and production 
ready"|https://lists.apache.org/thread.html/5ad2d854789e9e39ff286b8d4bc01594e50b8be92f707f6eba96ef6d@%3Cgeneral.hadoop.apache.org%3E]
* [Hadoop PMC labeled 2.9.0 as "wait for future 
releases"|https://lists.apache.org/thread.html/1a2544aee2be113a00e3930b708d37e001902f7f8275cf01031b9d4b@%3Ccommon-dev.hadoop.apache.org%3E]
 (some more background in a [subthread on the 2.9.0RC0 
VOTE|https://lists.apache.org/thread.html/5c61da56de36e1b38fb16c02e4cd66ee1284bf18a521add5d4443ac3@%3Ccommon-dev.hadoop.apache.org%3E])
* [Hadoop PMC labeled 2.8.3 as 
"GA"|https://lists.apache.org/thread.html/4fcec5d01714c4a19bae4da1694a8da7baa8c84b522e2fad086b80e7@%3Ccommon-dev.hadoop.apache.org%3E]
 (also fixes 
[CVE-2017-15713|https://lists.apache.org/thread.html/a790a251ace7213bde9f69777dedb453b1a01a6d18289c14a61d4f91@%3Cgeneral.hadoop.apache.org%3E]
 which impacts 2.8.2 but doesn't look severe enough for us to proactively wave 
people off of impacted releases)

I believe that brings us up to date on Hadoop's branches 2. There was some 
rumbling on a 2.9.1 release that got quiet and there's an ongoing discussion 
about the future of Hadoop branch 2 minor releases (including the possibility 
that they might bump minimum jdk versions in a 2.y minor release (!!!)), so we 
can wait ~months to revisit this again.

> Update ref guide for hadoop versions to include 2.8 and 2.9
> -----------------------------------------------------------
>
>                 Key: HBASE-19983
>                 URL: https://issues.apache.org/jira/browse/HBASE-19983
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: Mike Drob
>            Assignee: Sean Busbey
>            Priority: Major
>




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

Reply via email to