Dear Flink Community,

Thanks for putting all that effort into the 1.14 release. We are now post 
feature freeze and it looks like most of the features made it. This will be a 
decent release.

Here's a summary of today's bi-weekly, which has been a bit longer.

*Exception for feature freeze*
There are two efforts around FLIP-147 and the Kafka source which have some 
pending PRs. The people driving that forward will (or already did) reach out to 
the mailing list and ask for the exception to merge it.

*1.14 release wiki page*
Please keep the page [1] up to date. To mark well documented and tested 
features we are introducing the new state "done done". Please mark a feature as 
"done done", when it is well documented and tested. Please add issues or PRs 
for documentation to the corresponding column, as well as tickets that can be 
picked up by other teams for cross-team testing.

*Cleaning up issues*
When there was a parent issue targeting the 1.14 release and there are 
remaining, open subtasks please move them to a new ticket and close the old one 
for the sake of transparency and clarity.

*Documentation*
During the stabilisation phase documentation issues will be handled as blockers 
as they also have an impact on test-ability.

*Cross-team testing*
As mentioned above, those responsible for a feature should create a ticket for 
cross-team testing containing instructions to test the newly developed feature. 
This should be linked on the wiki page. Others should pick some of those and 
test features they did not contribute to.

*Build stability*
The last weeks the build stability has been awful, which somehow comes natural 
as a lot of features have been just merged. Now, this is blocking us from 
moving towards a first release candidate. We encourage every contributor to 
look into those issues and pick some to improve the general CI experience. The 
release managers will try to find assignees for the blockers as soon as they 
appear and for the critical issues during the syncs. Please ensure to report 
issues with the right severity and fix version.

You can use the Kanban board to get an overview and pick up issues. There are 
filters ready to use for 1.14 related blockers, critical issues, instabilities 
and cross-team testing issues. So once again: make sure the fixVersion is set 
to "1.14.0" to let issues appear on this board. [2]

*Syncs*
From now on the syncs will happen weekly (Tuesdays, same time, same place). If 
the load for the release managers is too high we will move to two meetings per 
week. In the syncs we will go through the blockers and assign unassigned 
critical issues.

*Release branch and RC0*
As we want to collect user feedback as early as possible, we'd like to push for 
branching of the release and creating the first release candidate as soon as 
possible. This requires work on stability issues. (see above). We will decide 
in the sync next week about the timing.

Thanks for making this happen.

Best Xintong, Dawid & Joe

[1] https://cwiki.apache.org/confluence/display/FLINK/1.14+Release
[2] https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=468

Reply via email to