Hi Thomas!
Thank you for raising your concerns.
I agree that we should document the compatibility guarantees that we expect
to provide going forward.
Since releasing 0.1 (v1alpha1) we added a great deal of new core features.
This required some modification to the CR obviously but actually it onl
I think before we release 1.0, we need to define and document the
compatibility guarantees.
At the moment, the CR changes frequently and as was pointed out
earlier, there isn't any automation to ensure changes are backward
compatible. In addition, our documentation still refers to upgrade as
a pr
Thanks Gyula. It looks good to me. I could do a favor during the release
also.
Please feel free to ping me to help the doc, release and test work :)
Best,
Aitozi
Yang Wang 于2022年5月16日周一 21:57写道：
> Thanks Gyula for sharing the progress. It is very likely we could have the
> first release candida
Thanks Gyula for sharing the progress. It is very likely we could have the
first release candidate next Monday.
Best,
Yang
Gyula Fóra 于2022年5月16日周一 20:50写道：
> Hi Devs!
>
> We are on track for our planned 1.0.0 release timeline. There are no
> outstanding blocker issues on JIRA for the release.
Hi Devs!
We are on track for our planned 1.0.0 release timeline. There are no
outstanding blocker issues on JIRA for the release.
There are 3 outstanding new feature PRs. They are all in pretty good shape
and should be merged within a day:
https://github.com/apache/flink-kubernetes-operator/pull/
Thanks @Chesnay Schepler for pointing out this.
The only public interface the flink-kubernetes-operator provides is the
CRD[1]. We are trying to stabilize the CRD from v1beta1.
If more fields are introduced to support new features(e.g. standalone mode,
SQL jobs), they should have the default valu
Hi Gyula,
Thanks for the release timeline information. I would like to learn the gathered
knowledge and volunteer as well. Will there be sync up meeting/call for this
collaboration ?
From: Gyula Fóra
Date: Monday, April 25, 2022 at 11:22 AM
To: dev
Subject: [DISCUSS] Next Flink Kubernetes Ope
me to leave it
to next major release.
Thanks all guys again for the awesome work.
Best,
Biao Geng
获取 Outlook for iOS<https://aka.ms/o0ukef>
发件人: Aitozi
发送时间: Tuesday, April 26, 2022 10:59:39 PM
收件人: dev@flink.apache.org
主题: Re: [DISCUSS] Next Flink Kubernet
uesday, April 26, 2022 10:59:39 PM
收件人: dev@flink.apache.org
主题: Re: [DISCUSS] Next Flink Kubernetes Operator release timeline
Thanks Gyula for starting this discussion.
The release time looks good to me. The main code for the session job is
complete,
the doc and other side issues are on the way.
Thanks Gyula for starting this discussion.
The release time looks good to me. The main code for the session job is
complete,
the doc and other side issues are on the way. I will ping you guys in the
ticket
after the work are completed from my side to help review together whether
there is functiona
Thanks Gyula for starting this discussion.
Some users from different companies are also very interested in
flink-kubernetes-operator project and asked me in private when it will be
production ready.
Now I would say the release 1.0.0 aims to this mission.
Given that the SQL support in flink-kubern
11 matches
Mail list logo
