[
https://issues.apache.org/jira/browse/FLINK-30965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias Pohl reassigned FLINK-30965:
-------------------------------------
Assignee: Matthias Pohl
> git-repo-sync doesn't pick up the 2nd-most-recently published Flink version
> (even though it's still supported) after a new release branch is cut
> ------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: FLINK-30965
> URL: https://issues.apache.org/jira/browse/FLINK-30965
> Project: Flink
> Issue Type: Bug
> Components: Test Infrastructure
> Reporter: Matthias Pohl
> Assignee: Matthias Pohl
> Priority: Major
>
> I noticed that we're always synchronizing the most-recent release branches
> (see
> [flink-ci/git-repo-sync:git-repo-synch:27|https://github.com/flink-ci/git-repo-sync/blob/7c0c2ed4b8f1cdf343e75021ca89e9dcc9421b93/sync_repo.sh#L27]).
> That means that we stop running CI on the Flink version that is soon to be
> deprecated after a new release branch is cut, e.g.: 1.16 & 1.15 are supported
> and we cut {{release-1.17}} to start the release process for 1.17. From this
> point onwards, we are synchronizing 1.17 and 1.16 but skip 1.15 eventhough
> 1.15 is still supported.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
