On Mon, 29 Aug 2022 at 23:01, Brandon Williams wrote:
> +1 for removing it when we add 17, to avoid making extra work.
>
+1 on that^
Let me look into how much work it would take to get accord building with jdk8,
that may create the least amount of work for everyone involved.
> On Aug 29, 2022, at 2:42 PM, Ekaterina Dimitrova
> wrote:
>
> We will need also Jenkins, cassandra-builds. We need to add also j11 upgrade
> tests a
Going to be OOO the rest of this week so I figured I'd hit up a bit under the 2
week mark.
4.1:
Pretty big spike in test failures on the latest run. The Butler dashboard here:
https://butler.cassandra.apache.org/#/, and the details here:
https://butler.cassandra.apache.org/#/ci/upstream/compare
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
cre
Off the top of my head I know all the packages are built with java8
right now, so those tests would fail. I don't think there's any of it
that is too difficult, it's just going to be a lot of little things
that are probably easier to do in one pass instead of two.
Kind Regards,
Brandon
On Mon, A
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 accor
+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 wrote:
>
> Sorry, I meant trunk, not 4.1 :)
>
> > On Aug 29, 2022, at 1:09 PM, Blake Eggleston wrote:
> >
> > Hi all, I wanted to propose removing jdk8 support fo
Yes I'd seen the 11+17 thread, but didn't see anything about an explicit jdk8
removal (ie: removal from CI etc). Ekaterina informed me there was an earlier
thread covering that though
> On Aug 29, 2022, at 1:09 PM, Blake Eggleston wrote:
>
> Hi all, I wanted to propose removing jdk8 support fo
+1 (nb) on removing java8 support from trunk.
On 2022/08/29 20:42:18 "J. D. Jordan" wrote:
> +1 for removing on trunk. Pretty sure we already discussed that in the Java
> 17 thread? That trunk will move to 11+17?
>
> > On Aug 29, 2022, at 3:40 PM, Blake Eggleston wrote:
> >
> > Sorry, I mean
+1 for removing on trunk. Pretty sure we already discussed that in the Java 17
thread? That trunk will move to 11+17?
> On Aug 29, 2022, at 3:40 PM, Blake Eggleston wrote:
>
> Sorry, I meant trunk, not 4.1 :)
>
>> On Aug 29, 2022, at 1:09 PM, Blake Eggleston wrote:
>>
>> Hi all, I wanted t
Sorry, I meant trunk, not 4.1 :)
> On Aug 29, 2022, at 1:09 PM, Blake Eggleston 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 uncontrove
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
12 matches
Mail list logo
