Hello,

Last Tuesday was our second bi-weekly.

You can read up the outcome in the confluence wiki page [1].

*Feature freeze date*
As we didn't come to a clear agreement, we will keep the anticipated feature 
freeze date
as it is at early August.

*Build stability*
The good thing: we decreased the number of issues, the not so good thing: only 
by ten.
We as a community need to put further effort into this.

*Dependencies*
We'd like to ask all contributors to have a look at the components they are 
heavily 
Involved with to see if any dependencies require updating. There were some 
Issues recently to pass the security scans by some of the users. In future this 
should
somehow be a default at the beginning of every release cycle.

*Criteria for merging PRs*
We want to avoid merging PRs with unrelated CI failures. We are quite aware 
that we
need to raise the importance of the Docker caching issue.

What can you do to make the Flink 1.14. release a good one:
* Identify and update outdated dependencies
* Get rid of test instabilities
* Don't merge PRs including unrelated CI failures

Best,
Joe


[1] https://cwiki.apache.org/confluence/display/FLINK/1.14+Release

Reply via email to