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.
Given that the Operator itself is not strictly bound to Flink versions it can be upgraded independently from the runtime versions it manages. It would benefit the community to have frequent minor releases until the majority of the roadmap items are complete that also encourages users to upgrade regularly in reasonable boundaries. Based on some offline discussion with Gyula Fora I would like to propose the following operational model for Operator releases: - time-based release cadence with 2 month release cycles ( This would give us roughly 6 weeks pure dev time and leave 2 weeks for the release process to finish) - on-demand patch releases for critical issues only - support the current and previous minor releases with bug fixes I am looking forward to your feedback and suggestions on this topic. Once we have an agreement I will formalize it on a Wiki page. Thanks, Matyas
