[jira] [Commented] (FLINK-17844) Activate japicmp-maven-plugin checks for @PublicEvolving between bug fix releases (x.y.u -> x.y.v)

["Chesnay Schepler (Jira)" <ji...@apache.org>]

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

Chesnay Schepler commented on FLINK-17844:
------------------------------------------

tooling added in:
master: 5fc54bb4d056130c3c666859d7980d544eb82e64
1.11: 55aea3535204b2612bd7527b70cbc99a455827c6 
1.10: 58139c78bb1745f0cfcf887c3501292e7f3ad1eb

> Activate japicmp-maven-plugin checks for @PublicEvolving between bug fix releases (x.y.u -> x.y.v)
> --------------------------------------------------------------------------------------------------
>
>                 Key: FLINK-17844
>                 URL: https://issues.apache.org/jira/browse/FLINK-17844
>             Project: Flink
>          Issue Type: New Feature
>          Components: Build System
>            Reporter: Till Rohrmann
>            Assignee: Chesnay Schepler
>            Priority: Critical
>              Labels: pull-request-available
>             Fix For: 1.11.0
>
>
> According to https://lists.apache.org/thread.html/rc58099fb0e31d0eac951a7bbf7f8bda8b7b65c9ed0c04622f5333745%40%3Cdev.flink.apache.org%3E, the community has decided to establish stricter API and binary stability guarantees. Concretely, the community voted to guarantee API and binary stability for {{@PublicEvolving}} annotated classes between bug fix release (x.y.u -> x.y.v).
> Hence, I would suggest to activate this check by adding a new {{japicmp-maven-plugin}} entry into Flink's {{pom.xml}} which checks for {{@PublicEvolving}} classes between bug fix releases. We might have to update the release guide to also include updating this configuration entry.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)