[
https://issues.apache.org/jira/browse/HBASE-22155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16811098#comment-16811098
]
Sean Busbey commented on HBASE-22155:
-------------------------------------
github doesn't show the branch either. so it must just be the local git's view
of the remote that's messed up. let me see if we can easily clean that up.
> Move 2.2.0 on to hbase-thirdparty-2.2.0
> ---------------------------------------
>
> Key: HBASE-22155
> URL: https://issues.apache.org/jira/browse/HBASE-22155
> Project: HBase
> Issue Type: Sub-task
> Components: thirdparty
> Reporter: stack
> Assignee: stack
> Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: HBASE-22155-branch-2.2-001.patch,
> HBASE-22155-branch-2.2-001.patch, HBASE-22155-branch-2.2-001.patch,
> HBASE-22155-branch-2.2-001.patch, HBASE-22155-branch-2.2.v004.patch,
> HBASE-22155.branch-2.2.001.patch, HBASE-22155.branch-2.2.002.patch,
> HBASE-22155.branch-2.2.003.patch, HBASE-22155.branch-2.2.004.patch,
> HBASE-22155.branch-2.2.005.patch
>
>
> hbase-thirdparty-2.2.0 was just released. The 2.2.0 RM ([~zghaobac]) gave his
> blessing in parent issue that 2.2.0 should use thirdparty 2.2.0.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
