Hi Everyone, We are on the verge of starting the release process for Flink 1.3.2 and there have been some critical issues in both Flink 1.3.0 and 1.3.1. For Flink 1.3.2 I want to make very sure that we test as much as possible. For this I’m proposing a slightly changed testing procedure [1]. This is similar to the testing document we used for previous releases but has a new functional testing section that tries to outline a testing procedure and a combination of systems/configurations that we have to test. Please have a look and comment on whether you think this is sufficient (or a bit too much).
What do you think? Best, Aljoscha [1] https://docs.google.com/document/d/16fU1cpxoYf3o9cCDyakj7ZDnUoJTj4_CEmMTpCkY81s/edit?usp=sharing
