On Tue, 20 Mar 2018 16:26:30 -0500, you wrote:
>So this is basically Oracle imposing a rapid upgrade path on free users to
>force them to buy commercial to get LTS stability?
>
>This will probably shake out in the community somehow. Cassandra is complex
>but we are small fry in the land of IT
On Wed, 21 Mar 2018 14:04:39 +0100, you wrote:
>There's also another option, which I just want to mention here for the
>sake of discussion.
>
>Quoting the Oracle Support Roadmap:
>"Instead of relying on a pre-installed standalone JRE, we encourage
>application developers to deliver JREs with
On Fri, 23 Mar 2018 15:52:51 +, you wrote:
>Java 8 was marked as EOL in the middle of last year, I hope we wouldn't
>require it for Cassandra 4. At this point I feel like we should already be
>targeting Java 10 at a minimum.
Given that the last messages indicated aiming Cassandra 4 for the
On Wed, 21 Mar 2018 10:52:06 -0400, you wrote:
>> Even if you are not running say Debian, or RedHat, those distributions
>> will be backporting critical fixes to their JVMs; This work is going
>> to be done, and will be available to anyone.
>This would certainly mitigate a lot of the core
On Fri, 23 Mar 2018 04:54:23 +, you wrote:
>I think Michael is right. It would be impossible to make everyone follow
>such a fast release scheme, and supporting it will be pressured onto the
>various distributions, M$ and Apple.
>On the other hand https://adoptopenjdk.net has already done a
On Tue, 5 Apr 2022 12:20:49 +0100, you wrote:
>I would strongly recommend keeping Python 3.6 compatibility until
>2024-06-30 when the CentOS 7 maintenance updates is stopped.
I would point out that the RHEL 8.* (as seen on Rocky Linux 8.5)
releases come with Python 3.6 and I don't see anything
