The whole release plan sounds good to me. Thanks for driving this.
Best,
Yang
Gyula Fóra 于2022年3月23日周三 16:22写道：
> Hi Team!
>
> I think we are in good shape to cut the preview release branch in a few
> days and start testing.
> I suggest we aim for a feature freeze on Friday the 25th (except
Hi Team!
I think we are in good shape to cut the preview release branch in a few
days and start testing.
I suggest we aim for a feature freeze on Friday the 25th (except for the
ongoing session job work which might need 1-2 extra days) and cut the
release branch on Monday the 28th (and hopefully
Hi all
Thanks for starting the discussion. The first release at the end of
March looks good to me, I think the flink-kubernetes-operator is in a good
shape now. I will try to complete the design to support the session job in
these two days and will start another discussion before the work.
Hi Gyula,
Thanks for the quick response. And your answers to the questions sound good
to me.
I'd suggest first creating a "Creating a Flink Kubernetes Operator Release"
page and a "Verifying a Flink Kubernetes Operator Release" page on the
wiki[1], just like other projects. We can then discuss /
Hi Xintong!
Thank you for the valuable input, you are completely right we need to agree
and document these aspects.
Let me try to address some of the questions and others should chip in also
:)
1. Version convention:
I think we should adopt the 3 digit versioning scheme like other flink
How everyone,
It's great to learn that we are approaching a preview release for
the flink-kubernetes-operator. Thanks for the efforts.
I have not been involved with any developing efforts in
flink-kubernetes-operator, thus have no comment on end of March being the
targeting date.
However, based
Hi there,
It is exciting to see the discussion of the release timeline! I agree that
the end of March is a proper date.
To make others easier get involved in this discussion, I think we may need
to provide a more straightforward feature list for the preview release. The
"Initial Feature Set" in
@Konstantin: Yes I completely agree that for this release the API (CRD)
should be marked experimental!
I have opened a ticket to track this:
https://issues.apache.org/jira/browse/FLINK-26620
@Yang Wang : I think we still have plenty of time
to work on features like the session job before the
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
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
10 matches
Mail list logo
