[
https://issues.apache.org/jira/browse/HBASE-27206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17567526#comment-17567526
]
Viraj Jasani edited comment on HBASE-27206 at 7/17/22 7:14 AM:
---------------------------------------------------------------
Although we are keeping 2.5.0 in fix version, we should be ready for limiting
backports till 2.6.0 as well because now I feel merging the change, testing it
with -perf validations- functional validations etc might take longer than 1
week and 2.5.0 RC1 seems around the corner.
Keeping this till 2.6.0 would also bake the changes on branch-2 for sometime
and give us reasons to move there faster than how longer it took for 2.4.0 ->
2.5.0 journey.
was (Author: vjasani):
Although we are keeping 2.5.0 in fix version, we should be ready for limiting
backports till 2.6.0 as well because now I feel merging the change, testing it
with perf validations etc might take longer than 1 week and 2.5.0 RC1 seems
around the corner.
Keeping this till 2.6.0 would also bake the changes on branch-2 for sometime
and give us reasons to move there faster than how longer it took for 2.4.0 ->
2.5.0 journey.
> Clean up error-prone findings in hbase-common
> ---------------------------------------------
>
> Key: HBASE-27206
> URL: https://issues.apache.org/jira/browse/HBASE-27206
> Project: HBase
> Issue Type: Sub-task
> Reporter: Andrew Kyle Purtell
> Assignee: Andrew Kyle Purtell
> Priority: Major
> Fix For: 2.5.0, 3.0.0-alpha-4
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
