[
https://issues.apache.org/jira/browse/FLINK-33009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17800696#comment-17800696
]
Wencong Liu edited comment on FLINK-33009 at 12/27/23 6:42 AM:
---------------------------------------------------------------
Hi [~mapohl] , I've encountered the same issue once more in [FLINK-33949]
METHOD_ABSTRACT_NOW_DEFAULT should be both source compatible and binary
compatible - ASF JIRA (apache.org)when I'm making some code changes considered
binary incompatible by japicmp. I'd like to take this ticket and fix it. WDYT?
was (Author: JIRAUSER281639):
Hi [~mapohl] , I've encountered the same issue once more when I'm making some
code changes considered binary incompatible by japicmp. I'd like to take this
ticket and fix it. WDYT?
> tools/release/update_japicmp_configuration.sh should only enable binary
> compatibility checks in the release branch
> ------------------------------------------------------------------------------------------------------------------
>
> Key: FLINK-33009
> URL: https://issues.apache.org/jira/browse/FLINK-33009
> Project: Flink
> Issue Type: Bug
> Components: Release System
> Affects Versions: 1.19.0
> Reporter: Matthias Pohl
> Priority: Major
>
> According to Flink's API compatibility constraints, we only support binary
> compatibility between versions. In
> [apache-flink:pom.xml:2246|https://github.com/apache/flink/blob/aa8d93ea239f5be79066b7e5caad08d966c86ab2/pom.xml#L2246]
> we have binary compatibility enabled even in {{master}}. This doesn't comply
> with the rules. We should this flag disabled in {{master}}. The
> {{tools/release/update_japicmp_configuration.sh}} should enable this flag in
> the release branch as part of the release process.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
