Table of contents

Jira Boards

Flink 1.19 Burndown: 1.19 Burndown - Agile Board - ASF JIRA (apache.org)

Sync meeting

• The release sync will start from Nov 7th, 2023, at 10am (UTC+2) and 4pm (UTC+8). The release sync happens bi-weekly at first, and will be adjusted to weekly as we approaching the feature freeze date. 
• Feel free to join on Google Meet. 

Timeline

• Feature Freeze
  
  • Jan 26, 2024, 00:00 CEST(UTC+2) 
• Release
  • End of Feb 2024

Highlight features

please feel free to add/suggest.

Features

List of features announced by contributors and committers that are likely to be ready for the feature freeze:n

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. Of course, unless fixing a bug is a really big or important one equivalent to implementing a completely new feature. 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.

Legend

State

symbol	meaning	comment
	validated	through cross team testing
	done	well documented with a complete test coverage
	will make it	there is no reason this effort should not go into 1.19
	in danger	there are some concerns the effort could be ready for the feature freeze of 1.19
	very unlikely	there are severe concerns the effort could make it to 1.19
	won't make it	it was decided against adding this for the 1.19 release. working on the effort has been stopped.
	state unclear
	independent	as the artifact could be released independent of Apache Flink

X-Team verification

symbol	meaning
	done
	not required

Feature Stage

Please align with the list on the Apache Flink Roadmap (https://flink.apache.org/roadmap.html).

• MVP: Have a look, consider whether this can help you in the future.
• Beta: You can benefit from this, but you should carefully evaluate the feature.
• 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.
• Stable: Unrestricted use in production
• Reaching End-of-Life: Stable, still feel free to use, but think about alternatives. Not a good match for new long-lived projects.
• Deprecated: Start looking for alternatives now 

Summary

Numbers are based on the items in the list below, not on the tickets 

									∑	Remaining weeks

List

Feel free to add categories.

Runtime
Name/JIRA Issue	Responsible Contributor	Reviewer / committer available	Feature Stage	Note	State	%	Updated	Implemented	Documented	X-team verified
Shuffle
Coordination
FLIP-379: Dynamic source parallelism inference for batch jobs	Xia Sun			under discussion
State & Checkpoint
Unable to render Jira issues macro, execution error.	Hangxiang Yu
REST
Configuration
FLIP-366: Support standard YAML for FLINK configuration				accepted
SQL
Name/JIRA Issue	Responsible Contributor	Reviewer / committer available	Feature Stage	Note	State	%	Updated	Implemented	Documented	X-team verified
Unable to render Jira issues macro, execution error.	Jane Chan
Unable to render Jira issues macro, execution error.	@Yangze Guo
Connectors
Unable to render Jira issues macro, execution error.	Fang Yong Qingsheng Ren
Unable to render Jira issues macro, execution error.	Leonard Xu
Resource Management
Runtime
Misc
FLIP-375: Built-in cross-platform powerful java profiler	Yu Chen

Status / Follow-ups

11/07/2023

• Is Google Meet OK for everyone? 
• Retrospective of 1.18
• Daily work divisions
  
  • JIRA ticket (Mainly focus on new blockers, progress of existing blockers each week) 
  • CI (Failures reported in #build channel and not reported)
  • Benchmark (Check if there's regression in the #flink-dev-benchmarks channel)
  • Mailing list monitoring
  • This division doesn't mean that other RMs are now allowed to do the work. All RMs should take responsibilities on all of these daily issues if they are available. 
• Feature freezing date.