[jira] [Assigned] (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:all-tabpanel ]

Chesnay Schepler reassigned FLINK-17844:
----------------------------------------

    Assignee: Chesnay Schepler

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