We will need also Jenkins, cassandra-builds. We need to add also j11
upgrade tests and fix some other inconsistencies what jobs we run. I have
it on my list and some things partially ready. And I am sure I am missing
something.
As I said in Slack, I am not against, just trying to be optimal and
creating less noise when/where it is possible and be efficient so that
people on all ends can progress with whatever they work on. Let’s talk to
Mick and put down the pin-points and assess the plan? How about that?

On Mon, 29 Aug 2022 at 17:25, Blake Eggleston <beggles...@apple.com> wrote:

> Can you say some more about what extra work you expect removing jdk8 to
> cause? I'd expect removing jdk8 to be mostly subtractive (from build.xml
> and circleci confs), and jdk17 support to be mostly additive.
>
> We're getting ready to merge the first set of accord integration patches,
> and the accord library requires java11+. My understanding is that jdk17
> support in C* is still several months away, so if we can avoid making one a
> dependency on the other, that would be preferable.
>
>
> On Aug 29, 2022, at 2:01 PM, Brandon Williams <dri...@gmail.com> wrote:
>
> +1 for removing it when we add 17, to avoid making extra work.
>
> Kind Regards,
> Brandon
>
> On Mon, Aug 29, 2022 at 3:40 PM Blake Eggleston <beggles...@apple.com>
> wrote:
>
>
> Sorry, I meant trunk, not 4.1 :)
>
> On Aug 29, 2022, at 1:09 PM, Blake Eggleston <beggles...@apple.com> wrote:
>
> Hi all, I wanted to propose removing jdk8 support for 4.1. Active support
> ended back in March of this year, and I believe the community has built
> enough confidence in java 11 to make it an uncontroversial change for our
> next major release. Let me know what you think.
>
> Thanks,
>
> Blake
>
>
>
>

Reply via email to