> Do we still need to support Java 8 SDK?
Yes, for Google Cloud customers who still use Java 8, I want Apache Beam to
support Java 8. Do you observe any special burden maintaining Java 8?
Regards,
Tomo
On Tue, Nov 29, 2022 at 21:48 Austin Bennett wrote:
> -1 for ongoing Java8 support [ or,
-1 for ongoing Java8 support [ or, said another way, +1 for dropping
support of Java8 ]
+1 for having tests that run for ANY JDK that we say we support. Is there
any reason the resources to support are too costly [ or outweigh the
benefits of additional confidence in ensuring we support what we
It looks that there is again the same issue with
beam_PostCommit_Website_Publish job - the last successful build was 6 days ago.
Could someone take a look on this?
Thanks,
Alexey
> On 11 Oct 2022, at 19:23, David Huntsperger via dev
> wrote:
>
> Thank you!
>
> On Mon, Oct 10, 2022 at 8:18
Hello,
I’m sorry if it’s already discussed somewhere but I find myself a little bit
lost in the subject.
So, I’d like to clarify this - what is a current official state of Java 17
support at Beam?
I recall that a great job was done to make Beam compatible with Java 17 [1] and
Beam already
This is your daily summary of Beam's current high priority issues that may need
attention.
See https://beam.apache.org/contribute/issue-priorities for the meaning and
expectations around issue priorities.
Unassigned P1 Issues:
https://github.com/apache/beam/issues/24389 [Failing Test]:
