Hi everyone, can we mark all the APIs as experimental/alpha so that it is clear that these can be broken in future releases for now? I think this would be very important given the early stage of the project. We want to be able to address shortcomings without worrying too much about backwards compatibility at this stage, I believe.
Cheers, Konstantin On Sun, Mar 13, 2022 at 7:48 AM Yang Wang <danrtsey...@gmail.com> wrote: > Thanks Gyula for starting this discussion. > > Given that the core functionality is closing to stable, I am in favor of > having the MVP release at the end of March. > The first release will help us to collect more feedbacks from the users. > Also it is a good chance to let the users know that the community is trying > to maintain an official Kubernetes operator :) > I hope that the companies could build their own production streaming > platform on top of the flink-kubernetes-operator in the future. > > FYI: @Wenjun Min is still working hard on supporting the Session Job in > Flink Kubernetes operator, It will be great if we could include it in the > first release. > And I believe we have enough time. > > Moreover, I agree with you that we need to invest more time in the > documentation, e2e tests, helm install optimization, logging, > etc. before the release. > > > Best, > Yang > > > Gyula Fóra <gyf...@apache.org> 于2022年3月12日周六 01:10写道： > > > Hi Team! > > > > I would like to discuss the timeline for the initial preview/milestone > > release of the flink-kubernetes-operator > > <https://github.com/apache/flink-kubernetes-operator> project. > > > > The last few weeks we have been working very hard with the community to > > stabilize the initial feature set and I think we have made great > progress. > > While we are still far from a production ready-state, a preview release > > will give us the opportunity to reach more people and gather much needed > > input to take this project to the next level. > > > > There are still a couple missing features that we need to iron out and we > > need to make sure we have proper documentation but after that I think it > > would be a good time for the preview release. > > > > I propose to aim for the first release candidate around the 25-27th of > > March after which we should dedicate a few days for some extensive > testing > > and bugfixing. > > > > What do you think? > > > > Gyula > > > -- Konstantin Knauf https://twitter.com/snntrable https://github.com/knaufk
