Re: [DISCUSS] Flink Kubernetes Operator release cadence proposal

2022-06-27 Thread Őrhidi Mátyás
Hi Devs, I've created the wiki page Release Schedule and Planning for the Operator. Let's keep it up-to-date :) Thank you all for your valuable inputs! Cheers, Matyas On Mon, Jun 27, 2022 at 10:14 AM Őrhidi Mátyás

Re: [DISCUSS] Flink Kubernetes Operator release cadence proposal

2022-06-27 Thread Őrhidi Mátyás
Thanks, Gyula, working on it. Will update the thread today. Thanks, Matyas On Mon, Jun 27, 2022 at 9:10 AM Gyula Fóra wrote: > Matyas, I think we have an agreement here :) > > It would be nice if you could add a release plan page to the wiki for the > operator to formalize this. Then at the beg

Re: [DISCUSS] Flink Kubernetes Operator release cadence proposal

2022-06-27 Thread Gyula Fóra
Matyas, I think we have an agreement here :) It would be nice if you could add a release plan page to the wiki for the operator to formalize this. Then at the beginning of each release cycle we could agree on larger features to be included in the upcoming release. For now the only large work-in-pr

Re: [DISCUSS] Flink Kubernetes Operator release cadence proposal

2022-06-22 Thread Márton Balassi
Thanks for the proposal, Matyas. +1 for 2 month release cycles with the breakdown Gyula suggested. @Yang: we could start tagging features with 1.1 / 1.2 version then, good call. On Wed, Jun 22, 2022 at 4:58 AM Yang Wang wrote: > +1 for 2 month release cycles. > > Since we have promised the bac

Re: [DISCUSS] Flink Kubernetes Operator release cadence proposal

2022-06-21 Thread Yang Wang
+1 for 2 month release cycles. Since we have promised the backward compatibility for CRD, I think it is also reasonable for us to maintain the latest two minor versions with patch releases. Given that we only have 5~6 weeks for feature development, maybe we need to confirm down the features as so

Re: [DISCUSS] Flink Kubernetes Operator release cadence proposal

2022-06-21 Thread Gyula Fóra
Hi Matyas! Thanks for starting the discussion. I think the 2 month release cycle sounds reasonable. I think it's important for users to have frequent operator releases as these affect all Flink jobs running in the environment. We should also only adopt a schedule that we can most likely keep. If

[DISCUSS] Flink Kubernetes Operator release cadence proposal

2022-06-21 Thread Őrhidi Mátyás
Hi Devs, After the successful Kubernetes Operator 1.0.0 release, which is considered to be the first production grade one, it is probably a good time now to also agree on a predictable release cadence for the Operator too, similarly to the time-based release plan we have for the Flink core project