[
https://issues.apache.org/jira/browse/BOOKKEEPER-735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13917803#comment-13917803
]
Sijie Guo commented on BOOKKEEPER-735:
--------------------------------------
if you want to introduce those tickets in 4.2, please re-open them and mark the
fix versions as 4.2.3. so the committers will pick the changes into 4.2 branch,
so we could keep all the commit histories in that branch, which is also
respecting to the works made by the contributors.
> Merge PerChannelBookieClient goodness from trunk to 4.2 branch
> --------------------------------------------------------------
>
> Key: BOOKKEEPER-735
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-735
> Project: Bookkeeper
> Issue Type: Bug
> Components: bookkeeper-client
> Affects Versions: 4.2.2
> Reporter: Rakesh R
> Assignee: Rakesh R
> Fix For: 4.2.3
>
> Attachments: 0001-BOOKKEEPER-735_br_4_2.patch
>
>
> In trunk we have done good imprv/bug fixes to perChannelBookieClient, I feel
> its worth to merge the necessary changes into 4.2 branch too.
> Included the following jira issues:
> # BOOKKEEPER-688
> # BOOKKEEPER-714
> # BOOKKEEPER-726
> # BOOKKEEPER-602 (from this, merge the logging of timed out entries).
--
This message was sent by Atlassian JIRA
(v6.2#6252)
