[GitHub] flink issue #6240: [FLINK-9004][tests] Implement Jepsen tests to test job av...
Github user tillrohrmann commented on the issue: https://github.com/apache/flink/pull/6240 Nice, thank you. Merging this PR. ---
[GitHub] flink issue #6240: [FLINK-9004][tests] Implement Jepsen tests to test job av...
Github user GJL commented on the issue: https://github.com/apache/flink/pull/6240 I extended the regular `README.md`. ---
[GitHub] flink issue #6240: [FLINK-9004][tests] Implement Jepsen tests to test job av...
Github user GJL commented on the issue: https://github.com/apache/flink/pull/6240 It seems that we have to stick with `0.1.8` for now. According to legal, there are no concerns so far: https://issues.apache.org/jira/browse/LEGAL-392 ---
[GitHub] flink issue #6240: [FLINK-9004][tests] Implement Jepsen tests to test job av...
Github user GJL commented on the issue: https://github.com/apache/flink/pull/6240 `0.1.9.` was problematic. Currently testing `0.1.10`. ---
[GitHub] flink issue #6240: [FLINK-9004][tests] Implement Jepsen tests to test job av...
Github user tillrohrmann commented on the issue: https://github.com/apache/flink/pull/6240 Gary is reaching out to Apache legal to ask for advice how to handle the SOLIPSISTIC license. Apparently, we cannot easily upgrade to `0.1.10` because it contains a bug. ---
[GitHub] flink issue #6240: [FLINK-9004][tests] Implement Jepsen tests to test job av...
Github user zentol commented on the issue: https://github.com/apache/flink/pull/6240 Note that this may also imply that the files that we add cannot be apache licensed, but I'm not completely sure about that. ---
[GitHub] flink issue #6240: [FLINK-9004][tests] Implement Jepsen tests to test job av...
Github user tillrohrmann commented on the issue: https://github.com/apache/flink/pull/6240 I think you are right @zentol because we are linking against Jepsen `0.1.8` and Jepsen was licensed under EPL only in version `0.1.10`. ---
[GitHub] flink issue #6240: [FLINK-9004][tests] Implement Jepsen tests to test job av...
Github user zentol commented on the issue: https://github.com/apache/flink/pull/6240 My information is outdated, they updated the license roughly a month ago to EPL: https://github.com/jepsen-io/jepsen/commit/d9c8530b7a2deac2389d93639581dfa1ff0f08fc ---
[GitHub] flink issue #6240: [FLINK-9004][tests] Implement Jepsen tests to test job av...
Github user tillrohrmann commented on the issue: https://github.com/apache/flink/pull/6240 Where exactly do you see the license conflicts @zentol? We do not include Jepsen code in our repository and since it is licensed under EPL 1.0 we should be able to link against it. ---
[GitHub] flink issue #6240: [FLINK-9004][tests] Implement Jepsen tests to test job av...
Github user zentol commented on the issue: https://github.com/apache/flink/pull/6240 The jepsen license is not compatible with the apache license and thus must be part of the release. ---
[GitHub] flink issue #6240: [FLINK-9004][tests] Implement Jepsen tests to test job av...
Github user tillrohrmann commented on the issue: https://github.com/apache/flink/pull/6240 Concerning @zentol's comment: We also include the `flink-end-to-end-tests` in the source release. Therefore, I think we could also include the jepsen-tests in the src release. Especially since one can execute them easily via `docker-compose`. ---
[GitHub] flink issue #6240: [FLINK-9004][tests] Implement Jepsen tests to test job av...
Github user GJL commented on the issue: https://github.com/apache/flink/pull/6240 As @zentol mentioned, we might want to exclude this from create_source_release.sh. ---
