[jira] [Commented] (BOOKKEEPER-589) Release notes update for non-BC changes

["Rakesh R (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/BOOKKEEPER-589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14159108#comment-14159108 ] 

Rakesh R commented on BOOKKEEPER-589:
-------------------------------------

I failed to see {{Incompatible change}} field in JIRA, we could update the same to show the compatibility status. I just checked other hadoop projects there is a custom field {{Hadoop Flags}} which has this checkbox (for example : ZK, HDFS projects etc). Also, they have {{Release Note}} field. Truly, I didn't know whether these will be automatically picked up and reflects in the release notes, since others are using I feel these would be useful in projects. It seems admin/infra has to provide these custom fields in the project. Is there any request flow to the infra team to add extra fields into the project jira?


> 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)