Dear community,

I've noticed that Flink has grown quite a bit in the past. As a consequence
it can be quite challenging to stay up to date. Especially for community
members who don't follow Flink's MLs on a daily basis.

In order to keep a bigger part of the community in the loop, I wanted to
try out a weekly update letter where I update the community with what
happened from my perspective. Since I also don't know everything I want to
encourage others to post updates about things they deem important and
relevant for the community to this thread.

# Weekly update #12:

## Flink 1.5 release:
- The Flink community is still working on the Flink 1.5 release. Hopefully
Flink 1.5 can be released in the next weeks.
- The main work concentrated last week on stabilizing Flip-6 and adding
more automated tests [1]. The Flink community appreciates every helping
hand with adding more end to end tests.
- Consequently, the committed changes mainly consisted of bug fixes and
test hardening.
- By the end of this week, we hope to have a RC ready which can be used for
easier release testing. Given the big changes (network stack and Flip-6),
the RC will most likely still contain some rough edges. In order to smooth
them out, it would be good if we run Flink 1.5 in as many different
scenarios as possible.

## Flink 1.3.3. has been released
- Flink 1.3.3 containing an important fix for properly handling checkpoints
in case of a DFS problem has been released. We highly recommend that all
users running Flink 1.3.2 upgrade swiftly to Flink 1.3.3.

## Misc:
- Shuyi opened a discussion about improving Flink's security [2]. If you
are interested and want to help with the next steps please engage in the
discussion.

PS: Don't worry that you've missed the first 11 weekly community updates.
It's just this week's number.

[1]
http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/ANNOUNCE-Flink-1-5-release-testing-effort-td21646.html
[2]
http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/DISCUSS-Flink-security-improvements-td21068.html

Cheers,
Till

Reply via email to