+1 to such a table. While the Go SDK is still experimental, when that changes it would be reasonable to ensure that the SDK releases function for the supported Go versions at their time of release. Only two released Go versions are supported by the Go team at a time (in terms of bugfixes and security patches) and the language has a twice annual release cycle.
On Tue, Jun 16, 2020, 4:37 PM Kyle Weaver <kcwea...@google.com> wrote: > The Java [1] and Python [2] quickstart pages list these > requirements, among other places. Even if we add a table, there's no > guarantee that people will actually look at it before asking these > questions on Stack Overflow. > > It might help though if we also add the supported versions to the Java and > Python SDK landing pages as well. > > [1] https://beam.apache.org/get-started/quickstart-java/ > [2] https://beam.apache.org/get-started/quickstart-py/ > > On Tue, Jun 16, 2020 at 11:20 AM Ning Kang <ni...@google.com> wrote: > >> Hi! >> >> Recently, I've seen questions around using incompatible JDK versions and >> Python versions with Beam on Stackoverflow. For example, this question >> <https://stackoverflow.com/questions/57017337/what-is-the-latest-version-of-jdk-used-by-apache-beam> >> about JDK and this question >> <https://stackoverflow.com/questions/62387489/gcp-dataflow-template-creation-issue-through-python-sdk/> >> about using Python 3.8. >> >> As we move Beam version forward, is there a public document continuously >> updated that tells the user of below information, like: >> >> Beam version >> >> JDK version range >> >> Python version range >> >> WIP >> >> 2.22.0 >> >> 8 >> >> 2, 3.5, 3.6, 3.7 >> >> BEAM-2530 <https://issues.apache.org/jira/browse/BEAM-2530> >> >> ... >> >> ... >> >> ... >> >> ... >> >> So that when they set up or maintain their project, they have a clear >> idea of what works, what will work and what will not work in the future? >> >> Thanks! >> >> Ning. >> >>
