[
https://issues.apache.org/jira/browse/BOOKKEEPER-589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14143102#comment-14143102
]
Ivan Kelly commented on BOOKKEEPER-589:
---------------------------------------
This issue would involve no code change, I only created it to remind the
release manager to update the release notes. The release notes will be
generated from jira, but we always update them a little before publishing them
to the website (adding template etc). This is where the warning about the
upgrade order should go. Also it should be mentioned in the release email. Once
the release manager remembers to do this, then this jira can be marked as Won't
fix (and fix version 4.3.0 removed, as it doesn't actually change anything in
code). It would be nice to be able to have jira take care of adding extra
release notes directly, but I can't see anywhere online how to configure this.
Regarding BOOKKEEPER-575, that's for SSL and that won't go in until 4.4.0. A
prereq for SSL is protobufs being used over the wire. This is what
BOOKKEEPER-582 [1] introduced, and this is what breaks compatability. A 4.3.0
client will not work with a 4.2.3 server. A 4.2.3 client will work with a 4.3.0
server though.
[1] despite what the issue description says, it does include over the wire
> 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)
