Hey Gyula,

+1 for the 1.14.0 release. I agree, it would be good for someone to
prepare the release who hasn't done a release yet.

Cheers,
Max

On Mon, Jan 19, 2026 at 10:19 PM Daniel Rossos via dev
<[email protected]> wrote:
>
> Hi Gyula,
>
> Thanks so much for the response, we have just wrapped up our PRs and
> flipped them to ready-for-review.
>
> *Networking Update / Ingress not Stable* - FLINK-38577
> <https://issues.apache.org/jira/browse/FLINK-38577>, PR
> <https://github.com/apache/flink-kubernetes-operator/pull/1049>
>
> *Metrics for FlinkBlueGreenDeployment *- FLINK-38787
> <https://issues.apache.org/jira/browse/FLINK-38787>, PR
> <https://github.com/apache/flink-kubernetes-operator/pull/1052>
>
> *FlinkBlueGreenDeployment Pipeline Suspension* - FLINK-38915
> <https://issues.apache.org/jira/browse/FLINK-38915>, PR
> <https://github.com/apache/flink-kubernetes-operator/pull/1053>
>
> *FlinkBlueGreenDeploytment savepointRedeployNonce fixes *- FLINK-38867
> <https://issues.apache.org/jira/browse/FLINK-38867>, PR
> <https://github.com/apache/flink-kubernetes-operator/pull/1051>
>
> James and I will be very easy to reach over the next few weeks to integrate
> any feedback / discuss changes.
>
> Thanks again and have a great rest of your day,
>
> Daniel
>
> On Thu, Jan 15, 2026 at 3:23 AM Gyula Fóra <[email protected]> wrote:
>
> > Hi Daniel!
> >
> > With targeting the end of Jan release cut, we should be able to merge most
> > of these fixes if you have PRs on the way.
> >
> > Please open the PRs with the fixes when you are ready and then we see what
> > fits into this release reasonably.
> > We can always delay the cut with a few days to wrap in progress PRs up.
> >
> > Cheers
> > Gyula
> >
> > On Wed, Jan 14, 2026 at 5:03 PM Daniel Rossos via dev <
> > [email protected]>
> > wrote:
> >
> > > Hi Gyula,
> > >
> > > Thanks for starting this discussion. The Shopify team has been working on
> > > several FlinkBlueGreenDeployment fixes and additions that would round out
> > > the Blue-Green functionality. If we are planning on releasing the
> > > FlinkBlueGreenDeployment functionality as part of 1.14.0 it could be
> > > worthwhile to include these fixes we've been developing.
> > >
> > > Here's our current work and status:
> > >
> > > *Networking Update / Ingress not Stable* - FLINK-38577
> > > <https://issues.apache.org/jira/browse/FLINK-38577>
> > > - Draft PR exists
> > > <https://github.com/apache/flink-kubernetes-operator/pull/1049>on OSS
> > > awaiting prelim review + full review:
> > >
> > > *Metrics for FlinkBlueGreenDeployment *- FLINK-38787
> > > <https://issues.apache.org/jira/browse/FLINK-38787>
> > > - Reviewed internally in fork and should be ready for OSS review
> > imminently
> > >
> > > *FlinkBlueGreenDeployment Pipeline Suspension* - FLINK-38915
> > > <https://issues.apache.org/jira/browse/FLINK-38915>
> > > - Development in progress on fork
> > >
> > > *FlinkBlueGreenDeploytment savepointRedeployNonce fixes *- FLINK-38867
> > > <https://issues.apache.org/jira/browse/FLINK-38867>
> > > - Development in progress on fork
> > >
> > > Let me know what you think about including these changes and if
> > > FlinkBlueGreenDeployments are planned for this release. We're happy to
> > > provide any support needed.
> > >
> > > Thanks,
> > > Daniel
> > >
> > >
> > >
> > > On Wed, Jan 14, 2026 at 6:42 AM Gyula Fóra <[email protected]> wrote:
> > >
> > > > Hi All!
> > > >
> > > > We had the last operator release at the end of september. Since then we
> > > > have accumulated a few important fixes and changes.
> > > >
> > > > Looking at the pending PRs I think we would be in a good position to
> > > > release 1.14.0 at the end of january / beginning of february.
> > > >
> > > > My recommendation would be to cut the release on January 30 and
> > test/vote
> > > > on the RC in the first week of Feb.
> > > >
> > > > I am happy to prepare the release myself but if someone is interested
> > to
> > > be
> > > > a release manager for this one, I am also here to help.
> > > >
> > > > Cheers
> > > > Gyula
> > > >
> > >
> >

Reply via email to