[
https://issues.apache.org/jira/browse/HBASE-22155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16811113#comment-16811113
]
Sean Busbey commented on HBASE-22155:
-------------------------------------
okay forcing a new git clone has worked to remove the stale branch and yetus
can properly tell that this is for branch-2.2 again.
https://builds.apache.org/job/PreCommit-HBASE-Build/16669/
> 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.004.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)
