- How to work just yuri 1.15 how to#
- How to work just yuri 1.15 update#
- How to work just yuri 1.15 upgrade#
Not much progress due to occupied in version upgrade story.
How to work just yuri 1.15 how to#
How to deal with class loader leaks in the TableAPI?. New sink interface has wrong numRecordsOut metric. Ask if all items are tagged with the right fixed version. Are the right issues shown up on this board?. 
How to work just yuri 1.15 update#
Teams responsible for components should update wether we want to really do stuff about 1.15. FLINK-26281 Konstantin will assign himself and ask someone who might be able to do it. FLINK-26191 Fabian & team will have a look at it. Blocker & Critical issues on board: (47 remaining). Create release testing and documentation issues?. Cutting branch might put more pressure on the CI. Will ask for cross team testers after meeting. Numbers are based on the items in the list below, not on the tickets Deprecated: Start looking for alternatives now. Not a good match for new long-lived projects. Reaching End-of-Life: Stable, still feel free to use, but think about alternatives. Ready and Evolving: Ready to use in production, but be aware you may need to make some adjustments to your application and setup in the future, when you upgrade Flink. Beta: You can benefit from this, but you should carefully evaluate the feature. MVP: Have a look, consider whether this can help you in the future. Please align with the list on the Apache Flink Roadmap ( ). working on the effort has been stopped.Īs the artefact could be released independent of Apache Flink It was decided against adding this for the 1.15 release. There are severe concerns the effort could make it to 1.15 There are some concerns the effort could be ready for the feature freeze of 1.15 There is no reason this effort should not go into 1.15 Well documented with a complete test coverage A good rule of thumb would be that each entry in the page could (but does not have to) be later on included in a release blog post. Of course, unless fixing a bug is a really big or important one equivalent to implementing a completely new feature. NOTICE: It's preferred if only new features end up there and not all bugs/tasks separately, so that the page is not over bloated. List of features announced by contributors and committers that are likely to be ready for the feature freeze:n (pushed by a week on the 27th of January and due again due to CI issues on the 14th of February). 
Feel free to join on Dingtalk Timelineįeature Freeze Monday, 14th 16th of February 2022, end of business CEST. As we are getting closer to the feature freeze we will do the meeting on a weekly base starting on the 25th of January. The sync meeting is happening every second Tuesday starting on the 16th of November at 9am CET / 4pm CST.
0 kommentar(er)
