You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Matthias Pohl (Jira)" <ji...@apache.org> on 2023/08/31 08:18:00 UTC

[jira] [Updated] (FLINK-33009) tools/release/update_japicmp_configuration.sh should enable binary compatibility checks in the release branch

     [ https://issues.apache.org/jira/browse/FLINK-33009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matthias Pohl updated FLINK-33009:
----------------------------------
    Summary: tools/release/update_japicmp_configuration.sh should enable binary compatibility checks in the release branch  (was: tools/release/update_japicmp_configuration.sh)

> tools/release/update_japicmp_configuration.sh should 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)