by-and-large I'm quite happy with the list of items.

I'm curious as to why the "Disaggregated State Management" item is marked as a must-have; will it require changes that break something? What prevents it from being added in 2.1?

We may want to update the Java 17 item to "Make Java 17 the default, drop Java 8/11". Maybe even split it into a must-have "Drop Java 8" and a nice-to-have "Drop Java 11"?

"Move Calcite rules from Scala to Java": I would hope that this would be an entirely internal change, and could thus be an incremental process independent of major releases.
What is the actual scale of this item; how much are we actually re-writing?

"Add MetricGroup#getLogicalScope": I'd raise this to a must-have; i think I marked it down as nice-to-have only because it depends on another item.

The ProcessFunction API item is giving me the most headaches because it's very unclear what it actually entails; like is it an entirely separate API to DataStream (sounds like it is!) or an extension of DataStream. How much will it share the internals with DataStream etc.; how does it relate to the Table API (w.r.t. switching APIs / what Table API uses underneath).

There are a few items I added as ideas which don't have a priority yet; would love to get some feedback on those.

On 21/06/2023 08:41, Xintong Song wrote:
Hi devs,

As previously discussed in [1], we had been collecting work item proposals
for the 2.0 release until June 15th, on the wiki page [2].

    - As we have passed the due date, I'd like to kindly remind everyone *not
    to add / remove items directly on the wiki page*. If needed, please post
    in this thread or reach out to the release managers instead.
    - I've reached out to some folks for clarifications about their
    proposals. Some of them mentioned that they can not yet tell whether we
    should do an item or not, and would need more time / discussions to make
    the decision. So I added a new symbol for items whose priorities are `TBD`.

Now it's time to collaboratively decide a minimum set of must-have items.
I've gone through the entire list of proposed items, and found most of them
make quite much sense. So I think an online sync might not be necessary for
this. I'd like to go with this DISCUSS thread, where everyone can comment
on how they think the list can be improved, followed by a VOTE to formally
make the decision.

Any feedback and opinions, including but not limited to the following
aspects, will be appreciated.

    - Important items that are missing from the list
    - Concerns regarding the listed items or their priorities

Looking forward to your feedback.

Best,

Xintong


[1]
https://lists.apache.org/list?dev@flink.apache.org:lte=1M:release%202.0%20status%20updates

[2]https://cwiki.apache.org/confluence/display/FLINK/2.0+Release

Reply via email to