[
https://issues.apache.org/jira/browse/FLINK-25348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17481717#comment-17481717
]
Chesnay Schepler commented on FLINK-25348:
------------------------------------------
Not cleaning it for patch releases has the added benefit that the japicmp
exclusion become a full reference of all breaking changes between 1.X.0 and
1.Y.Z, which is neat imo.
> Update release guide to reset japicmp exceptions for every release
> ------------------------------------------------------------------
>
> Key: FLINK-25348
> URL: https://issues.apache.org/jira/browse/FLINK-25348
> Project: Flink
> Issue Type: Sub-task
> Components: Build System
> Affects Versions: 1.15.0
> Reporter: Till Rohrmann
> Priority: Major
> Fix For: 1.15.0
>
>
> I propose to clean up the japicmp maven plugin exclusion for every minor
> release for @Public and the exclusions for @PublicEvolving with every patch
> release. Currently, we don’t do this and that’s why we have accumulated quite
> some list of exclusions that a) might shadow other problems and b) nobody
> really knows why they are still relevant. I would propose to make this part
> of the release guide. The result should be that we minimize our set of
> exclusions.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
