Hey Matthias,

it seems that there is no traction for creating another 1.18.x bugfix
release, so *I'm +1 for disabling CI for 1.18.*

On Wed, Dec 18, 2024 at 10:41 AM Matthias Pohl <map...@apache.org> wrote:

> Hi everyone,
> with the release of 1.20.0 [1], 1.18 reached its EOL. The community has
> decided to do a final "flush out" release in this case if it's requested
> (and, I guess, there is someone volunteering to do this). There was a
> question about release 1.18.2 [2] in the past. 1.18.2 contains 76 fixes
> [3].
>
> The reason I am asking is that we still have CI enabled for 1.18. It is
> failing constantly [4] which means we would have to resolve this first
> before releasing 1.18.2.
>
> Shall we add a grace period for this flush out release to happen to avoid
> having CI enabled for ever?
>
> Anyway, I would suggest disabling 1.18 CI and not pursuing the 1.18.2
> release considering that the only time it was raised was 8 month ago to
> save resources. Any opinions on that?
>
> Best,
> Matthias
>
> [1]
>
> https://flink.apache.org/2024/08/02/announcing-the-release-of-apache-flink-1.20/
> [2] https://lists.apache.org/thread/bhhkzsv8hkzbbt5ydqottbkgrlx2dfqt
> [3]
>
> https://issues.apache.org/jira/browse/FLINK-35728?jql=project%20%3D%20FLINK%20AND%20fixVersion%20%3D%201.18.2%20AND%20status%20IN%20(Resolved%2C%20Closed)%20ORDER%20BY%20updatedDate
> [4]
>
> https://dev.azure.com/apache-flink/apache-flink/_build?definitionId=1&_a=summary&repositoryFilter=1&branchFilter=37476%2C37476%2C37476
>

Reply via email to