Hi Devs! The community has been working hard on cleaning up the operator logic and adding some core features that have been missing from the preview release (session jobs for example). We have also added some significant improvements around deployment/operations.
With the current pace of the development I think in a few weeks we should be in a good position to release next version of the operator. This would also give us the opportunity to add support for the upcoming 1.15 release :) We have to decide on 2 main things: 1. Target release date 2. Release version With the current state of the project I am confident that we could cut a really good release candidate towards the end of May. I would suggest a feature *freeze mid May (May 16)*, with a target *RC0 date of May 23*. If on May 16 we feel that we are ready we could also prepare the release candidate earlier. As for the release version, I personally feel that this is a good time for *version 1.0.0*. While 1.0.0 signals a certain confidence in the stability of the current API (compared to the preview release) I would keep the kubernetes resource version v1beta1. It would also be great if someone could volunteer to join me to help manage the release process this time so I can share the knowledge gathered during the preview release :) Let me know what you think! Cheers, Gyula
