[
https://issues.apache.org/jira/browse/BOOKKEEPER-589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14143086#comment-14143086
]
Flavio Junqueira commented on BOOKKEEPER-589:
---------------------------------------------
I'm a bit confused here. This issue is a sub-task of BOOKKEEPER-575, and
BOOKKEEPER-575 is marked for 4.4.0. Do we need this release note on 4.3.0
because of some sub-task of BOOKKEEPER-575 that is already in? I'd really
appreciate some update here from [[email protected]].
I also had a look at the jira configuration and compared with the zookeeper
one, and I really can't understand why we can't see the release note field. We
might need to contact infra and ask.
> Release notes update for non-BC changes
> ---------------------------------------
>
> Key: BOOKKEEPER-589
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-589
> Project: Bookkeeper
> Issue Type: Sub-task
> Components: Documentation
> Reporter: Ivan Kelly
> Assignee: Ivan Kelly
> Priority: Blocker
> Fix For: 4.3.0
>
>
> 4.3.0 client will not be able to connect to 4.2.0 servers, due to something
> stupid in the protocol version handling. 4.2.0 and lower will blindly reject
> any messages which have a protocolVersion higher than that it's current
> version, even if the data format has not changed. The release notes should
> reflect this. Also, think about how the protocolVersion is used some more.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
