[jira] [Updated] (FLINK-33844) Update japicmp configuration

2024-01-16 Thread Jing Ge (Jira)


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

Jing Ge updated FLINK-33844:

Fix Version/s: 1.18.2
   (was: 1.18.1)

> Update japicmp configuration
> 
>
> Key: FLINK-33844
> URL: https://issues.apache.org/jira/browse/FLINK-33844
> Project: Flink
>  Issue Type: Sub-task
>Reporter: Jing Ge
>Assignee: Jing Ge
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.18.2
>
>
> Update the japicmp reference version and wipe exclusions / enable API 
> compatibility checks for {{@PublicEvolving}} APIs on the corresponding 
> SNAPSHOT branch with the {{update_japicmp_configuration.sh}} script (see 
> below).
> For a new major release (x.y.0), run the same command also on the master 
> branch for updating the japicmp reference version and removing out-dated 
> exclusions in the japicmp configuration.
> Make sure that all Maven artifacts are already pushed to Maven Central. 
> Otherwise, there's a risk that CI fails due to missing reference artifacts.
> {code:bash}
> tools $ NEW_VERSION=$RELEASE_VERSION releasing/update_japicmp_configuration.sh
> tools $ cd ..$ git add *$ git commit -m "Update japicmp configuration for 
> $RELEASE_VERSION" {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Updated] (FLINK-33844) Update japicmp configuration

2024-01-16 Thread Jing Ge (Jira)


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

Jing Ge updated FLINK-33844:

Affects Version/s: (was: 1.18.0)

> Update japicmp configuration
> 
>
> Key: FLINK-33844
> URL: https://issues.apache.org/jira/browse/FLINK-33844
> Project: Flink
>  Issue Type: Sub-task
>Reporter: Jing Ge
>Assignee: Jing Ge
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.18.1
>
>
> Update the japicmp reference version and wipe exclusions / enable API 
> compatibility checks for {{@PublicEvolving}} APIs on the corresponding 
> SNAPSHOT branch with the {{update_japicmp_configuration.sh}} script (see 
> below).
> For a new major release (x.y.0), run the same command also on the master 
> branch for updating the japicmp reference version and removing out-dated 
> exclusions in the japicmp configuration.
> Make sure that all Maven artifacts are already pushed to Maven Central. 
> Otherwise, there's a risk that CI fails due to missing reference artifacts.
> {code:bash}
> tools $ NEW_VERSION=$RELEASE_VERSION releasing/update_japicmp_configuration.sh
> tools $ cd ..$ git add *$ git commit -m "Update japicmp configuration for 
> $RELEASE_VERSION" {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Updated] (FLINK-33844) Update japicmp configuration

2024-01-16 Thread Jing Ge (Jira)


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

Jing Ge updated FLINK-33844:

Fix Version/s: 1.18.1

> Update japicmp configuration
> 
>
> Key: FLINK-33844
> URL: https://issues.apache.org/jira/browse/FLINK-33844
> Project: Flink
>  Issue Type: Sub-task
>Affects Versions: 1.18.0
>Reporter: Jing Ge
>Assignee: Jing Ge
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.18.1
>
>
> Update the japicmp reference version and wipe exclusions / enable API 
> compatibility checks for {{@PublicEvolving}} APIs on the corresponding 
> SNAPSHOT branch with the {{update_japicmp_configuration.sh}} script (see 
> below).
> For a new major release (x.y.0), run the same command also on the master 
> branch for updating the japicmp reference version and removing out-dated 
> exclusions in the japicmp configuration.
> Make sure that all Maven artifacts are already pushed to Maven Central. 
> Otherwise, there's a risk that CI fails due to missing reference artifacts.
> {code:bash}
> tools $ NEW_VERSION=$RELEASE_VERSION releasing/update_japicmp_configuration.sh
> tools $ cd ..$ git add *$ git commit -m "Update japicmp configuration for 
> $RELEASE_VERSION" {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Updated] (FLINK-33844) Update japicmp configuration

2024-01-16 Thread Jing Ge (Jira)


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

Jing Ge updated FLINK-33844:

Affects Version/s: 1.18.0

> Update japicmp configuration
> 
>
> Key: FLINK-33844
> URL: https://issues.apache.org/jira/browse/FLINK-33844
> Project: Flink
>  Issue Type: Sub-task
>Affects Versions: 1.18.0
>Reporter: Jing Ge
>Assignee: Jing Ge
>Priority: Major
>  Labels: pull-request-available
>
> Update the japicmp reference version and wipe exclusions / enable API 
> compatibility checks for {{@PublicEvolving}} APIs on the corresponding 
> SNAPSHOT branch with the {{update_japicmp_configuration.sh}} script (see 
> below).
> For a new major release (x.y.0), run the same command also on the master 
> branch for updating the japicmp reference version and removing out-dated 
> exclusions in the japicmp configuration.
> Make sure that all Maven artifacts are already pushed to Maven Central. 
> Otherwise, there's a risk that CI fails due to missing reference artifacts.
> {code:bash}
> tools $ NEW_VERSION=$RELEASE_VERSION releasing/update_japicmp_configuration.sh
> tools $ cd ..$ git add *$ git commit -m "Update japicmp configuration for 
> $RELEASE_VERSION" {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Updated] (FLINK-33844) Update japicmp configuration

2023-12-14 Thread Jing Ge (Jira)


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

Jing Ge updated FLINK-33844:

Fix Version/s: (was: 1.18.1)

> Update japicmp configuration
> 
>
> Key: FLINK-33844
> URL: https://issues.apache.org/jira/browse/FLINK-33844
> Project: Flink
>  Issue Type: Sub-task
>Reporter: Jing Ge
>Assignee: Jing Ge
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.19.0
>
>
> Update the japicmp reference version and wipe exclusions / enable API 
> compatibility checks for {{@PublicEvolving}} APIs on the corresponding 
> SNAPSHOT branch with the {{update_japicmp_configuration.sh}} script (see 
> below).
> For a new major release (x.y.0), run the same command also on the master 
> branch for updating the japicmp reference version and removing out-dated 
> exclusions in the japicmp configuration.
> Make sure that all Maven artifacts are already pushed to Maven Central. 
> Otherwise, there's a risk that CI fails due to missing reference artifacts.
> {code:bash}
> tools $ NEW_VERSION=$RELEASE_VERSION releasing/update_japicmp_configuration.sh
> tools $ cd ..$ git add *$ git commit -m "Update japicmp configuration for 
> $RELEASE_VERSION" {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Updated] (FLINK-33844) Update japicmp configuration

2023-12-14 Thread Jing Ge (Jira)


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

Jing Ge updated FLINK-33844:

Fix Version/s: (was: 1.19.0)

> Update japicmp configuration
> 
>
> Key: FLINK-33844
> URL: https://issues.apache.org/jira/browse/FLINK-33844
> Project: Flink
>  Issue Type: Sub-task
>Reporter: Jing Ge
>Assignee: Jing Ge
>Priority: Major
>  Labels: pull-request-available
>
> Update the japicmp reference version and wipe exclusions / enable API 
> compatibility checks for {{@PublicEvolving}} APIs on the corresponding 
> SNAPSHOT branch with the {{update_japicmp_configuration.sh}} script (see 
> below).
> For a new major release (x.y.0), run the same command also on the master 
> branch for updating the japicmp reference version and removing out-dated 
> exclusions in the japicmp configuration.
> Make sure that all Maven artifacts are already pushed to Maven Central. 
> Otherwise, there's a risk that CI fails due to missing reference artifacts.
> {code:bash}
> tools $ NEW_VERSION=$RELEASE_VERSION releasing/update_japicmp_configuration.sh
> tools $ cd ..$ git add *$ git commit -m "Update japicmp configuration for 
> $RELEASE_VERSION" {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Updated] (FLINK-33844) Update japicmp configuration

2023-12-14 Thread Jing Ge (Jira)


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

Jing Ge updated FLINK-33844:

Summary: Update japicmp configuration  (was: CLONE - Update japicmp 
configuration)

> Update japicmp configuration
> 
>
> Key: FLINK-33844
> URL: https://issues.apache.org/jira/browse/FLINK-33844
> Project: Flink
>  Issue Type: Sub-task
>Reporter: Jing Ge
>Assignee: Sergey Nuyanzin
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.19.0, 1.18.1
>
>
> Update the japicmp reference version and wipe exclusions / enable API 
> compatibility checks for {{@PublicEvolving}} APIs on the corresponding 
> SNAPSHOT branch with the {{update_japicmp_configuration.sh}} script (see 
> below).
> For a new major release (x.y.0), run the same command also on the master 
> branch for updating the japicmp reference version and removing out-dated 
> exclusions in the japicmp configuration.
> Make sure that all Maven artifacts are already pushed to Maven Central. 
> Otherwise, there's a risk that CI fails due to missing reference artifacts.
> {code:bash}
> tools $ NEW_VERSION=$RELEASE_VERSION releasing/update_japicmp_configuration.sh
> tools $ cd ..$ git add *$ git commit -m "Update japicmp configuration for 
> $RELEASE_VERSION" {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)